Add more checks and fix some callers to make sure that the server
core always has a valid screen layout configured.

It now accepts this parameter, so make sure it is documented.

We disabled it in 0a0e582 since it didn't have support for resizing.
But it got that support in 242c5b2, yet we forgot to allow this
setting again.

It doesn't belong on each socket server object as timers are global.
Force implementations to call the Timer system directly instead,
avoiding any middle men.

Do a proper cleanup when one of the termination timeouts trigger
rather than just exiting on the spot. This makes sure we don't leave
stray stuff around, e.g. unix socket files.

We might have an offset in the area of the screen we're tracking,
so make sure that offset is included in the changes we report.

We might only be using part of the X server's screen, so make sure
the layout we calculate is contained within this part.

This makes VNCServer a sufficiently complete interface that callers
don't need to know about the specific implementation (VNCServerST
currently). And assuming that all servers will use sockets is not
that outrageous.

Removed the last parts of VNCSConnectionST's back door in to
VNCServerST and let the parent class fully handle coordination of
clients, and access to the desktop.

Must be done in order to remove UNIX sockets etc.

Our main web site now supports https, so update all references.

Make things simpler by making this a part of the SDesktop interface
that always needs to be implemented.

Force queryConnection() to always call back to approveConnection()
rather than return special values. This makes the flow easier to
follow as it will be the same in all cases.

We cannot assume endian-ness for the cursor we get from XFixes.
Adjust the algorithm to properly follow the specification.

There are some cases where the server state will not automatically
be updated on a change. A prominent one is when only RFB attributes
were changes (e.g. the screen ID) but nothing else. In that case
there is no actual change in the X server, so it never sends any
notification about change back to us.

x0vncserver might only be observing part of the display, so we need
to adjust any coordinates before we give them to the RFB core.

The Xserver (at least Xorg 1.19) rejects RRSetCrtcConfig requests if
rotation is zero.

Makes the code more general and not directly tied to specifically
TCP sockets.

Change Xserver screen through libXrandr. For complex configurations,
all outputs must have corresponding size modes. As a special case, if
the client requests a single screen with an odd size (for example when
adjusting the size of a non-fullscreen vncviewer), find a smaller
suitable mode, and reduce the framebuffer size as well.

It wasn't properly updated in 3112f50 when it was split off from
x0vncserver.cxx.

In XDesktop::start() we allocate pixel buffer and set it as the backend to the given VNCServer.
In XDesktop::stop() we deallocate the buffer, so we must unset it from the VNCServer as well.
Otherwise the VNCServer could try to access it and crash, for example in deferred update.

Colour map support was removed in b6b4dc6, but x0vncserver didn't
properly check if the X server required it.

There were a bunch of parameters that weren't properly added to the
man pages when the features were added. Make sure everything is
properly in sync.

They share a lot of settings, so make sure the documentation is
identical in those cases.

The funcationality was removed in 6e49e95, so let's also clean up
the documentation referring to it.

XShmGetImage is much faster. On my machine, this reduces the CPU usage
of a fullscreen Youtube video playback from 40% to 25%.

Add a Configuration::removeParam to support such cases.

Legacy systems.

XFixes only reports cursor changes. We must manually call
XFixesGetCursorImage() when starting.

Define ledNames in XDesktop.cxx, rename N_LEDS to XDESKTOP_N_LEDS

No need for ifdefs; we can assume MITSHM. Already done in vncviewer.

It was only used by WinVNC, so push it there instead.

We would accidentally store they keycode 0 for unknown keysyms, wedging
the lookup table.

This is necessary to make sure the server side rendered cursor works
properly.

We never un-select it, and it's not a problem if we get extra ones so
register it once right away.

Use the client provided (using QEMU extendend key event) scancodes if
available instead of reverse mapping the keysym.

X11 unfortunately uses keyboard driver specific keycodes and provides
no direct way to query this, so guess based on the keyboard mapping.

Handle the two most likely keyboard drivers, the old xorgkbd and evdev.

Signed-off-by: Peter Korsgaard <peter.korsgaard@barco.com>

This adds the basic infrastructure and handshake for the QEMU
Extended Key Events extension. No viewer or server makes use of
the extra functionality yet though.

Listen for XKb XkbIndicatorStateNotify events for scroll/num/caps lock and
map them to the RFB protocol.

Signed-off-by: Peter Korsgaard <peter.korsgaard@barco.com>

Using XKeysymToKeycode() often gives the incorrect keycode as it
doesn't respect the current modifier state. Use XKB to find the
proper key instead.

This however also means that we need to track the mapping for all
pressed keys to make sure we know the correct keycode when it is
time to release the key.

https://github.com/TigerVNC/tigervnc/issues/361

This is a simple implementation that refetches and transforms the cursor
image every time it changes, and doesn't use the cursor naming functions
of the XFixes extension to save & cache cursor images.

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>