Better to avoid making unnecessary calls, but mainly we want to avoid
logging false errors.

For example, if we have earlier disabled an output because it was too
large for the framebuffer, we should prefer this output when
allocating new outputs.

Move the code that turn off unused outputs to the end.

Also, add support for checking the output connection state.

Apparently this is not necessary when using the internal API, but a
must with libXrandr.

This only matters when using clones, which we do not accept yet. This
patch is for completeness and to avoid future surprises.

Return error if no CRTC.

Screen is a Xvnc thing and not relevant for x0vncserver etc.

RANDR is mandatory since Xorg 1.7, which is the oldest version we
support.

In RandR land, there's a lot of return code confusion. Our wrappers
are using the same return codes as RRCrtcSet, RRScreenSizeSet: 1/TRUE
for success. Fixes:

* vncRandRCreateOutputs did not follow this convention

* A lot of code returned -1 upon failure

* vncRandRDisableOutput returned 0 for already disabled outputs

These two code blocks are not specific to Xvnc/vnc.so, but useful for
x0vncserver as well. RandrGlue.h defines the interface on which
unixcommon depends on.

Compatibility with libXrandr, where the name is in dynamically
allocated XRROutputInfo.

Less confusing, and compatible with libXrandr.

Should use 2 spaces like the rest of the project.

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.

TriFan and TriStrip were added in 1.12, so we need to have that code
conditional to support older versions of Xorg.

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.

We had overlooked a few so we didn't track all screen changes properly.

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

We need to flip the dimensions in the case the monitor is rotated
90° or they won't map correctly to the framebuffer.

No longer tolerate loading the VNC extension but not being able to
initialize it. This avoids a lot of error prone checking to see
if the extension has started fully or not.

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.

The normal Xorg server doesn't check this field, so neither can we
as there are applications relying on this leniancy.

It was moved to the common code in f8e3b34c6, but it was unreliable
because the state could sometimes get out of sync. Push it back in
to Xvnc since it isn't necessarily something all servers will have.

Otherwise we'll wedge the desktop object which expects an approval
or rejection to eventually show up.

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>