GitLab

Use QtVncServer as import for Qt Quick module, use the functions
from Qt's cmake scripts to automatically create a private module
and plugin pair (cargo-culting QtMultimediaQuickPrivate for this),
and use the conventional imports/ directory for the Qt Quick
module.

Copy the compositor manual test into an example.

Documentation, renaming a private header, some additional
build files.

A small example and some details in documentation.

Pitstop commit. Docs now generated, but not complete at all.

This is just a quick band-aid. The VncItem isn't registered for
1.0 in Qt 6, so my update to support Qt 5 broke it. So we have
separate tests until this can be resolved. There might be
something wrong with how we register the type, since it looks
like we need different import versions on Qt 5 and Qt 6.

Do this also the lazy way, since it's a temporary backport.

QQuickWindowPrivate::handleMouseEvent() rather than
deliverMouseEvent(). This works well for the test cases we
have.

Something off about mouse grabbing. The root item seems to always
grab the event. Easily reproducible with the testscene.qml

glDeleteFramebuffers() cannot be called directly for desktop GL
where we link to the GL library dynamically. It is also only
used from the ES2 code. Instead of adding additional #ifdef for
it, we just move it to grabTexture(), since deleting it from the
destructor, which is called from a different thread, is not valid
anyway.

It means we will create and destroy the ID every frame we capture,
but since it is just registering an ID, this should be fine.

This requires an enabler in Qt Declarative which exports
QQuickItemLayer.

Not implemented yet: Mouse support + ES2 support

Let each security type have its own state machine

Make it a settable property

Enabled automatically when LibTomCrypt is available. Password
hardcoded to 'ABCD' for testing.

This makes it possible to support additional security types, but
none are implemented yet.

Slightly hacky, but Wayland only handles keycodes and modifiers
in wl_keyboard, so the text is ignored.

The server encoding preference can now be customized with
QT_VNCSERVER_PREFERRED_ENCODING environment variable. Set this
to a semi-colon-separated list of encodings. The first that is
supported by the client will be picked. If none are supported
by the client, the client's first supported preference will be
chosen instead.

E.g.: QT_VNCSERVER_PREFERRED_ENCODING=hextile;zlib

This would make the server prefer hextile over zlib, even if the
client prefers zlib.

This still doesn't fix the Wayland issue, but at least now the
events generated from VNC are the same as the local events.

Don't grab frames when the client has not requested it. This should
improve local performance when we are animating at full FPS. This
can cause extra updates in the corner case where we are not animating
evenly and are unlucky with the timing.

Als add new logging category qt.vncserver.fps to show local and remote
FPS once per second.

It's overkill to do it every frame, but that's insignificant compared
to all the other work we do.

We were not actually doing anything on the client thread, since
the vnc client had been created as a child of the server, and
thus could not be moved. Fixing this revealed a bug in the
cleanup logic. We need to make sure we deleteLater() the
client objects and we need to quit and delete the client
thread from the main thread, after the client has been
deleted.