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

If scan codes are available using QEMU Extended Keyboard Messages
from clients, use that to inject scancodes directly into the
system using the SendInput API.

No conversion is needed as Windows uses the same scancode encoding.

Signed-off-by: Rahul Kale <Rahul.Kale@barco.com>
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.

LED support added using Windows GetKeyState() API call.

The state is polled for change in CapsLock/NumLock/ScrollLock
status in the same code block where chages to Cursor shape is polled.

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

This will allow us to use better formats that preserve the entire
alpha channel.

Use the platform independent primitives instead.

We've changed the service name a couple of times for various
reasons. Make sure the old versions are removed when the new one
is registered.

What to do when a socket is writeable should be handled in the
RFB core code as there may be other events we want to fire off
when this happens.

We have lots of code that deals with Windows versions that we no
longer support anyway. Clean out all of this old cruft.

We don't have any meaningful code for the mirror driver, so
remove the confusing stub and interface for it.

The identifier is used to compute the registry path, and should
ideally be kept short and without spaces.

The argument named "desc" was not actually the description, but
rather the short "display name". Add handling for the actual
description to reduce confusion.

It is easier to control object life time and avoid magical socket
duplication by having a single TcpListener object to pass around.
We have to be more careful about deleting the object though.

The IPv6 additions deprecated support for netmasks in the access
control lists. Unfortunately some documentation was not updated
to reflect this fact.

Avoids conflicts with the original RealVNC implementation, or any
other forks of that code.

It is needed by WinVNC, but got removed in 892d10a70. Also fix
a couple of issues:

 - Use getnameinfo() in order to be compatible with Windows XP
 - Make it static since it doesn't use a specific socket
 - Respect UseIPv4 and UseIPv6
 - Flags for getaddrinfo() that match binding code
 - Dummy service value for Windows compatibility

Solve it by casting to the larger of the two, i.e. 64-bit.

Either by casting, or switching to a more appropriate type
for the variable.

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.