This is where to install headers to, not where to find headers to
build against. Toolchains should know where to locate their system
headers while non-system headers should be found using
pkg-config. Users with bizarre setups where the toolchain really
cannot find the system headers should set CPPFLAGS.

There is a range of key codes that are never sent by a real keyboard
and are therefore used by layouts to hide "fake" mappings. Make sure
to only use these as a fallback as some applications get confused
when they see these codes.

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.

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.

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.

Applets don't work anymore so remove everything that has to do
with serving them.

Most layouts on Unix generate Meta for Shift+Alt but non-Unix clients
will send XK_Alt_*. This results in us picking some other key which
can confuse some applications.

Try to detect this scenario and map XK_Alt_* to XK_Meta_*.

We get a whole bunch of very tiny areas, which is very inefficient to
deal with. Instead create a rectangle around every "list" of connected
glyphs (usually each line).

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.

Function xorgGlxCreateVendor() is defined in glx_extinit.h, if this header is
not included, we might get either error or warning. This header also need to
be included after scrninststr.h header as it defines some structures used
in glx_extinit.h

In-server GLVND requires xorgGlxCreateVendor call from InitOutput.
DPMS functions were moved to another location and no longer need to be faked.
xserver120.patch is a copy of xserver119.patch with refreshed contexts.

Patch originally by Dag-Erling Smørgrav for University of Oslo.

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

With the new unixcommon library we have things outside of common/,
so make the handling of out-of-tree builds more general.

This can be used to test if a layout if possible.

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.

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.

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.

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.

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.