| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
The reason for this is to keep a consistency through out the project.
|
|
|
|
| |
The reason for this is to keep a consistency through out the project.
|
|
|
|
| |
The reason for this is to keep a consistency through out the project.
|
|
|
|
|
| |
Otherwise the compiler will complain about a defined but unused static
function.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Windows has (at least) two error namespaces, both errno and
GetLastResult(). These overlap, so it is important we keep track of
which one we are dealing with.
To make things extra problematic, the BSD socket API normally uses
errno, but on Windows it has been mapped in to the GetLastResult()
namespace.
Try to keep better control of this by using separate classes for the
namespaces.
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Only the client that currently has buttons pressed should actually send
a release event as the client might not be currently in control of the
pointer state. This is most clearly seen in a client that hasn't event
authenticated properly yet.
Approximate this from the server by using the last known server cursor
position. It should hopefully not differ much from the last client
provided position.
Follow-up to 986280b382d57ef4f68d2d4afb13b26772e5acb0.
|
|
|
|
|
| |
Prefer this exception for failures involving errno as it gives a better
error description.
|
|
|
|
|
| |
These functions return a GnuTLS status, so we should use the correct
exception for that so we get the proper error messages.
|
|
|
|
|
| |
This is the user actively rejecting the connection, and should be
signalled as such for correct behaviour.
|
| |
|
|
|
|
|
|
|
|
| |
There were more unclear usage of this exception class, and since nothing
catches it it is very unclear what the purpose is. Go ahead and just
remove it.
Follow-up to bcaaea7.
|
|
|
|
|
|
| |
Cursor data has a depth of 32 bits and hence cannot use CPIXELs.
This is a regression from baca73d.
|
|
|
|
|
| |
Problems with the original code: A process can only establish one connection.
After modification, multiple connections can be supported.
|
|
|
|
|
|
|
|
|
|
|
| |
sws_getCachedContext will set a default sampling method if 0 is passed
to the flags argument. This means that when it is called again, the
flags argument will not match the flags in the context, so a new one
will be allocated every time.
To get around this problem, we assign an explicit sampling method, one
that also happens to be more efficient and just as good for this
use-case as the default one, which is bicubic interpolation.
|
|
|
|
|
| |
The scaler is now informed of the colour space encoded into the stream
so that it may do the proper conversion.
|
|\ |
|
| |
| |
| |
| | |
This fixes a memory leak
|
| |
| |
| |
| |
| |
| |
| |
| | |
This ensures that the buffer is allocated with the correct alignment and
padding for use with sws_scale.
This fixes out-of-bounds writes which would in some cases cause
segmentation faults and/or heap corruption.
|
| |
| |
| |
| |
| |
| | |
The underlying issue requiring this hack was fixed ages ago.
Unfortunately, the fixed GnuTLS doesn't consider static linking. So we
need to add a new hack that permits that.
|
| |
| |
| |
| |
| | |
Try to be more clear about what things are external to the current
context, and what aren't.
|
| |
| |
| |
| |
| | |
The usage of this is unclear as it is never caught. Use the general
exception class, to stay consistent with all other protocol handling.
|
| |
| |
| |
| |
| | |
This was made obsolete in dd45b44 when we extended the serverInit()
callback.
|
| |
| |
| |
| |
| | |
This method is no longer blocking, so the description needed to be
adjusted.
|
| |
| |
| |
| | |
Let's try to mimic a real event as much as possible to avoid bugs.
|
| |
| |
| |
| |
| | |
This is a very limited bit field, so use an 8 bit type to clearly show
how many bits are available.
|
| |
| |
| |
| |
| | |
The different uses of this interface are not that closely related and
there is no need for them to have a common interface class.
|
| |
| |
| |
| | |
This has been unused since 9fe3479.
|
| |
| |
| |
| | |
This class has been removed since ages.
|
| |
| |
| |
| |
| | |
We need to return here or we'll do an out-of-bounds access on the data
array.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This exception is for when the user fails to authenticate, not all
possible errors that might occur during the authentication phase.
Use more appropriate exception types for the various other problems that
might occur, so that we can present things more accurately to the user.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This prefix often just added noise, and could sometimes be added
multiple times. It's better that user interface catch the specific
exception type and give a more descriptive presentation to the user.
This is partially a revert of 1922550.
|
| |
| |
| |
| |
| | |
We should not be throwing up error messages, or asking to reconnect, if
the user has actively cancelled the authentication attempt.
|
|/
|
|
|
|
|
|
|
|
|
| |
We implement our own version of this, and because of this we carry our
lookup table generated by the same tool that libX11 uses. Unfortunately,
that table is a global symbol and as such there might be a mismatch of
which table should be used.
Make sure we get our own copy by changing the name of it. We use a
define rather than modifying ks_tables.h as that file is automatically
generated.
|
|
|
|
|
| |
Otherwise it merges with the next entry, removing both of them from the
default list.
|
|
|
|
|
| |
This fixes a regression introduced by
12b3f4021641537b90727b23d42de5dff59006cd.
|
|
|
|
|
|
| |
The rounding misbehaved when the tv_usec calculation overflows.
Fixes issue #1782.
|
|
|
|
|
|
| |
As of 28c3f12, we might now be running the frame clock even without a
framebuffer present. This means we need to be more careful accessing the
ComparingUpdateTracker, as it might be NULL.
|
|
|
|
|
| |
Otherwise we won't properly guarantee that we'll wait *at least* as long
as the specified time.
|
|
|
|
|
| |
It's a source of confusion and possibly bugs to reuse the same variable
name for multiple things.
|
|
|
|
|
| |
Remove redundant arguments where the method already has access to the
relevant variable as an object attribute.
|
|
|
|
|
|
|
|
|
| |
These are often more readable as they avoid a lot of the boilerplate of
iterating over fixed arrays or STL containers.
Note that this change is very conservative to avoid noise in "git
blame". Only loops where this is a clear improvement have been
converted.
|
|
|
|
|
|
|
| |
Clients cannot remove themselves from the list as we are iterating, so
we don't need this complexity. If a client encounters a problem, it will
only mark it self as closed and will be removed from the list at a later
time.
|
|
|
|
|
| |
Let's avoid reimplementing something basic that's available in the
standard library. It also makes the code easier to read.
|
| |
|
|
|
|
|
| |
Use the new "override" keyword to properly differentiate between new
virtual methods, and existing virtual methods being overridden.
|
|
|
|
|
| |
It's more readable than 0, and a bit safer than NULL, so let's try to
follow modern norms.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Run the frame clock at a slow 1 Hz if there are no clients connected.
This is similar to what a normal X server does when the screen is
blanked, and should keep applications waiting for the frame tick happy.
Note that we still only keep the frame clock running if there is any
application that are interested in it. Otherwise we still stop it
completely.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If there is something interested in synchronizing to a frame tick, then
keep the frame clock running, even if there are no updates.
This is need mainly when something starts rendering, but also when
something renders much slower than the frame clock (so it is essentially
constantly "starting"). Such an application will not draw anything until
it gets a new frame tick, which it won't get as the frame clock is
waiting for something to start drawing.
|