| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This is a generic thing, not specific to the FLTK viewer. It belongs in
the core code.
|
|
|
|
|
| |
You need to activate the feature by setting supportsCursorPosition, so
there is no point in forcing everyone to implement the handler.
|
|
|
|
|
|
| |
We already had a field in the ServerParams structure, but we never
actually stored anything in it. Let's fix that so the cursor behaves
like other state we get from the server.
|
|
|
|
| |
These have never been used for anything and just clutter up the API.
|
|
|
|
|
| |
These are not per-client settings, so let's move the enforcement to the
common server object as much as possible.
|
|
|
|
|
|
| |
Access bits are part of SConnection, so let it handle all the basic
checks as well. This allows us to reduce the complexity of
VNCSConnectionST a bit.
|
|
|
|
|
|
| |
It's a bit confusing that some handling is done in
CMsgHandler/SMsgHandler, and some handling is done in
CConnection/SConnection.
|
|
|
|
|
|
| |
These are just for interactions internally within the connection objects
and their sub classes. Mark them as protected to make the API more
clear, and to avoid accidental use.
|
|
|
|
|
| |
Only override the actively used values, not the user values that are
stored and displayed in the options dialog.
|
|
|
|
|
|
|
| |
To be able to debug exactly what is wrong with the layout. Unfortunately
we don't know what log level is used for actual "invalid layout"
message, or if it is even logged as all, since that happens elsewhere.
So let's be cautious and use a debug log level here.
|
|
|
|
|
|
|
|
|
|
| |
Make sure everything on screen has a consistent look when the client
switches between different pixel formats.
Use the lossless refresh mechanism to make sure this doesn't interfere
with more important updates.
Based on a suggestion by Piotr Henryk Dabrowski.
|
|
|
|
|
|
|
|
| |
This is a revert of 0ce9fef. The object slicing is causing issues, e.g.
when we get a completely expected end_of_stream exception.
It's unclear what exceptions we needed this wrapping for. We'll just
have to remove it and see what problems we encounter.
|
|
|
|
| |
This is much more robust and flexible than what we came up with.
|
|
|
|
|
|
| |
It's rare, but there are some things that can go wrong in the
constructor for a new client object. Make sure we handle these and
properly close the socket, rather than leave it dangling.
|
|
|
|
| |
Broken in 4ff02ae.
|
| |
|
|
|
|
|
| |
The client should support all server security types by default. Unsure
why this was overlooked.
|
| |
|
| |
|
|
|
|
| |
We don't do multiple threads on the server, so this is not needed.
|
| |
|
|
|
|
| |
This should have been done as part of cf1bc66.
|
| |
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
We normally avoid specifying a class' own namespace prefix in order to
keep the code more compact. Region was the sole exception.
|
|
|
|
|
|
|
|
| |
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.
|
|\ |
|
| |
| |
| |
| |
| |
| | |
We've made the client more aggressive in resizing sessions, so this can
quickly produce a lot of log output. Reduce the log level to debug until
we can keep the stats for the entire session lifetime.
|
| |
| |
| |
| |
| |
| |
| | |
These are not needed since the cleanup in 6ea58ba.
At the same time, move the error logging for a failed SetDesktopSize to
the base CConnection class as it is a generic thing.
|
| | |
|
|/
|
|
| |
Broken in e97e225.
|
|
|
|
|
| |
Bad logic introduced in 28e35d0. Fortunately, nothing currently uses
this method.
|
|\ \ \
| | | |
| | | |
| | | | |
https://github.com/CendioOssman/tigervnc
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is a lot more readable than "0"/"1", which can easily be confused
with integer parameters.
Note that this breaks some backwards compatibility. Older clients will
not be able to parse configuration files generated by newer clients, as
they had a bug where they could only understand "0" and "1".
|
| | | |
| | | |
| | | |
| | | | |
Makes it much easier to find all the different options.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Now that we are based on a normal std::list, we can use normal iterators
to go through the parameters.
|
| | | |
| | | |
| | | |
| | | | |
Avoid rolling our own linked list when we have the standard library.
|