| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
(cherry picked from commit 4daa7b1172cd4606b60f8245831bc5aa155c4b9e)
|
|
|
|
|
|
|
|
|
|
| |
The previous FIXME was incorrect. The old code did in fact continue
looking over the entire area. This commit restores that old behaviour.
(cherry picked from commit eef5516854cdc466daed1e1a817bb41bc264027d)
Conflicts:
common/rfb/EncodeManager.cxx
|
|
|
|
|
|
|
| |
It had regressed in performance compared to 1.3. This brings it back
up to the same speed.
(cherry picked from commit a43a3f4e0e1ae9faa389a91ad9a38db4af4c54c8)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There were too many problems found so drop this functionality on
the stable branch. It will be revisited for the next release.
This reverts commit 4561f7e9c63c6ca2859da9b9fa75f64a1a8c2a81.
This reverts commit 6abf3f4c87a0309d5e7d436e4b72d26a08631ebf.
This reverts commit 820c0ceb2ed92080e8d76d50b78ba01bd264baef.
This reverts commit 698371a65002c8785c34481635044fddc217d3f1.
This reverts commit 6ae42df65141ccb49c875bda45b8f5ae9fa60c28.
This reverts commit f1665ac7fbff068ffc2c2f3f110645609b73806c.
This reverts commit 14263e17e425d1bca7e99d4ddfca1ace3bae0ca7.
This reverts commit 07cd2298dcbf7da8db22d630cb84c0216da30ea1.
This reverts commit 8e101704c32c47654d7453f5bde42d8d0c8cc160.
|
|
|
|
| |
They use char* rather than void*, requiring a cast here.
|
|
|
|
|
| |
This is the format we support when converting a string to an
address, so it makes sense to use them the other way around.
|
|
|
|
|
| |
There might be more protocols in the future, and we might also
misdetect things depending on varying IPv6 functions being missing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This reverts commit 39d7dc043afcf6f94b9c16942765fdb9a6a3202e.
We should be secure by default, even if it might cause a performance
hit. Those who wish to make that trade off are more likely to notice
the lack of performance than others noticing the lack of security.
|
|
|
|
|
| |
It's often useful to see if encryption was used, and how the user
authenticated (if at all).
|
| |
|
|
|
|
|
| |
We don't even log this much for RFB protocol stuff, and it makes
it very annoying to run with full debugging on.
|
|
|
|
| |
It is rdr and network that needs it, not vncviewer.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
| |
This was just plain wrong, so redo it properly.
|
| |
|
| |
|
|
|
|
|
|
| |
Having it in ConnParams made the linker pull all the encoder objects
into vncviewer, making it larger than necessary and giving it extra
parameters in its help output that weren't relevant.
|
| |
|
| |
|
|
|
|
|
| |
The input string might contain formatting marks, so make sure those
are ignored.
|
|
|
|
|
|
|
|
| |
This allows us to apply a lot more server logic
independently of which encoder is in use.
Most of this class are things moved over from the
Tight encoder.
|
|
|
|
| |
There is nothing using these classes anymore, so remove the clutter.
|
|
|
|
|
|
|
| |
This avoid a lot of unnecessary middle men. This also pushes the
responsibility for pixel format conversion into the encoders and
decoders. The new bufferFromBuffer() is used for direct conversion,
rather than PixelTransformer/TransImageGetter.
|
|
|
|
|
|
| |
Like we do for everything else. This also gets rid
of the callback, which is a bit out of place
compared to everything else.
|
| |
|
|
|
|
|
|
| |
Add a magical cursor framebuffer class for handling when you
want to render the cursor on the server side. Keeps the cursor
specific magic in one contained place.
|
| |
|
|
|
|
|
| |
Allows you to modify the buffer with data in a
different pixel format.
|
|
|
|
|
|
|
|
|
| |
Handles the common cases when the target or source are in
the preferred 888 format.
If one of the buffers is not 888, then it must also be properly
aligned (which is commonly the case). Performance is now in many
cases on par with PixelTransformer.
|
|
|
|
|
| |
This is a lot easier and cheaper than having to set up a complete
PixelTransformer object.
|
|
|
|
|
|
| |
You have to loop many times when converting e.g. 2 bits to 8,
so have a couple of lookup tables to speed things up. We still
use bit replication to get from 8 bits to 16 bits though.
|
|
|
|
|
| |
Allows pixel buffers that do damage tracking to get
proper information.
|
|
|
|
|
| |
Clearly separates the read API from the write API
and also from actual implementation.
|
|
|
|
|
|
| |
It was confusing and not properly used everywhere.
Callers should use the stride they get when they get
the buffer pointer.
|
| |
|
|
|
|
|
| |
Keep things simple instead and allows us to remove the extra setPF()
methods.
|
| |
|
| |
|
|
|
|
|
|
| |
The connection object is a much more appropriate object for the
decoders and encoders to keep track of. Besides the streams, it also
contains state like connection parameters.
|
|
|
|
|
| |
This keeps the reader and writer objects clean and simple protocol
decoders/encoders.
|
|
|
|
|
|
|
|
|
| |
Gets rid of a loooot of code and complexity.
Colour map clients are still supported through an
automatically generated map, but we lose the ability to
develop a client or server that uses colour maps
internally.
|
| |
|
|
|
|
| |
Keep the generic stream classes clean and general.
|