| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This should have been included way back in 674bf06.
|
|
|
|
| |
std::string doesn't like null strings. Give it an empty one instead.
|
|
|
|
| |
The compiler will flag this as a likely mistake otherwise.
|
|\ |
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
| |
OS abstractions are generic enough that we can merge these with the new
core library.
|
|
|
|
|
| |
These are general plumbing, so they fit in nicely with the new core
library.
|
|
|
|
|
| |
It's just string helper functions here, so let's get rid of the
catch-all name for this module.
|
|
|
|
|
|
|
|
| |
They weren't that well used, and were mostly just confusing special
functions anyway.
Allows us to move away from generic and ambigious headers such as
"util".
|
|
|
|
| |
Let's clear things up by categorizing our utility functions.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
| |
Make it clearer what is protocol handling and what is just general
plumbing.
This is one step of several.
|
|
|
|
|
|
|
|
| |
Try to keep the code more compact for the simple things where the type
should be obvious from the context. Helps us avoid line wrapping.
Also remove explicit conversions to Region where the compiler is able to
figure it out by itself, again to reduce line length.
|
|
|
|
|
| |
This is a network function, so it makes more sense in the network
library.
|
|
|
|
|
| |
Make compile times faster by reducing the number of headers included in
other headers.
|
|
|
|
| |
This inline class just makes this header overly complex.
|
| |
|
|
|
|
| |
It's not a formal name, so use regular case.
|
|\ \
| | |
| | |
| | | |
https://github.com/CendioOssman/tigervnc
|
| |/
|/|
| |
| |
| |
| |
| | |
We don't consistently use these, so they are just confusing.
Instead, we rely on the linker to not include unnecessary objects, and
hence irrelevant configuration objects.
|
|/
|
|
|
| |
Avoid duplicating this complexity everywhere and make sure all commands
get the same handling and fixes.
|
| |
|
|\ |
|
| |
| |
| |
| | |
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.
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds support for the pseudo-encoding ExtendedMouseButtons in
Xvnc and x0vncserver, which makes it possible to use to use the
back/forward mouse buttons.
This commit contains work originally done by
PixelSmith <manny33@frontbuffer.com>.
|
| | |
| | |
| | |
| | |
| | | |
This makes things more consistent since we mix with the standard library
exceptions so often.
|
| | |
| | |
| | |
| | |
| | | |
There is no point to having our own generic exception class. Let's use
the one provided by the standard C++ library.
|
| | |
| | |
| | |
| | |
| | | |
Use the more specific already included exception classes for common
errors to keep things more understandable.
|
| | |
| | |
| | |
| | |
| | | |
Make sure our exceptions are part of the standard exception class
hierarchy.
|
| |/
|/|
| |
| | |
Harmonize with the standard C++ exceptions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
|
|
| |
The behaviour is not consistent as Windows doesn't use errno for socket
errors, but Unix systems do. Always use the same exception to keep
things somewhat sane.
|
|
|
|
|
|
|
|
|
| |
This method should only be called when the client actually sends a
framebuffer update request, otherwise we might send data the client is
not ready for.
It's unclear what the purpose of this call is, so we have no better fix
than to just remove it.
|
|
|
|
|
| |
This is a very limited bit field, so use an 8 bit type to clearly show
how many bits are available.
|
|
|
|
|
| |
It's a source of confusion and possibly bugs to reuse the same variable
name for multiple things.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The desktop isn't completely paused just because there are no clients,
so it might still need some support from the server object.
This is primarily an issue for headless servers, where they need to
continue emulating things even without clients. A scraping server can
generally go completely passive if there are no clients.
|
| |
| |
| |
| |
| | |
It is much more sane to treat "0" as "a timer is ready NOW", so let's
change to using -1 as the invalid timeout value.
|