Don't assume a lack of TCP listeners means the server will be
unreachable. There might be other methods of access, so let the higher
levels do that sanity check instead.

The need for these must have got lost somewhere in the type cleanup.

All library functions should be in a proper namespace.

This mimics how some system functions (like inet_ntop()) work, and
avoids complexity around ownership of the returned string buffer.

The downside is that the string must be consumed directly as it will be
overwritten on the next call, but that is not an issue with the current
usage.

We don't need to make extra copies of the string in most cases, so let's
simplify the code and access the string directly when we can.

This allows us to separate accidentally unused, from explicitly unused
parameters, which allows us to turn on such checks in the compiler.

No practical difference currently, but let's respect what this API was
supposed to do.

These are general things and not specific to TigerVNC, so let's move it
to the fltk specific directory for clarity.

These have nothing to do with layout, so let's split them to their own
file.

Let's separate TigerVNC specific things from stuff that could be part of
upstream FLTK. These are files that we would like to collaborate with
other FLTK users, so they are more liberally licensed and avoid using
TigerVNC specific things.

Some desktop environment, like KDE, need more rastered sizes and cannot
make use of the SVG.

This code is never used on Windows, so remove it.

Avoid the risk of the list of sizes and the list of icons getting out of
sync and causing memory corruption.

The migration from 32-bit to 64-bit has long passed. Let's get rid of
all distinctions as native applications it the norm now.

Otherwise things might be logged under the wrong label.

The norm is to have error strings without punctiation, so avoid adding
one as it just confuses the translators.

vncviewer previously had a the same localized error message duplicated
on a bunch of places. Pull these duplicates out into a single function.

If you close the reconnect dialog then we should assume that you want to
close things, not that you want to reconnect. Unfortunately FLTK returns
the first choice when closing the dialog, so that needs to be the
"Cancel" alternative.

Try to reuse and split things so that it makes things easier for the
translators.

Try to be consistent with existing log messages.

Before this commit, `FullScreen` and `FullScreenAllMonitors` could be
used to configure whether to use the current monitor in fullscreen,
or all monitors in fullscreen.

This commit deprecates `FullScreenAllMonitors` in favour of
`FullScreenMode` (which can either be `current` or `all`). This allows
for additional modes to be added, without the risk of having invalid
states (for example two activate two different fullscreen modes at the
same time).

A new concept has been added; read-only parameters. They are parameters
that will be read, but never written back. This allows for migration
paths to be constructed, where a parameter can be taken to consideration
but then for example be discarded, logged or changed into something else.

This has been used for `FullScreenAllMonitors` to provide a migration
path. On startup of vncviewer, if `FullScreenAllMonitors` is enabled,
`FullScreenMode=all` will be automatically enabled instead. The next
time the configuration file is written to disk, `FullScreenAllMonitors`
will then be removed.

Let's avoid making this too complex and force every user to know about
magical functions.

We don't know the size of the output buffer here and giving the input
string size is just confusing and upsets the compiler in some cases.

This was already handled for most exit conditions, but not the early
ones.

This is needed by vncserver which doesn't know which parameters are
boolean, and it cannot use the -Param=Value form as that isn't tolerated
by the Xorg code.

Switch from using Core events to using X Input events for pointer
devices in order to differentiate between mouse events and touch events.

Because FLTK doesn't understand X Input 2, we intercept these events and
translate them to core events where possible.

We need to make sure everything happens in the correct order during
startup for the X11 display to open correctly. Primarily it means
we need to parse the arguments and open the display before anything
might make any X11 calls, as we may have a -display argument.

We don't exit here, so it's not a fatal error. It's also a fairly common
scenario, so remove the alert completely.

Include something more user friendly when we need to fail fatally and
not just the technical error.

Makes things more consistent and avoids surprises.

This makes our builds directly compatible with most distributions
without packagers/users having to specify extra flags.

We need to make sure it is null terminated on truncation. We also
need to avoid giving a too large size argument or modern gcc will
complain.

It's not common knowledge these days how X geometry is specified, and
even the man page X(7) is missing on many systems now.

FLTK has some options (that we've also documented in the man page)
that should be mentioned in the --help output.

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

We've had support for unix sockets for a while now. Make sure this
is reflected in the -help output and the man page.

Also make some minor tweaks to the section to get everything in
sync with reality.

We might not get one from the default configuration (we might not have
a default configuration at all), so make things more robust.

The user might just want to load a bunch of settings and not
initiate a connection.

The user can specify a tigervnc configuration file as an argument to the
viewer. Previously the viewer assumed this to be a server, but now we
will first check if there is any file matching the given argument. If
so, try to load the content of that file, like we normally do.

Fixes issue #38.

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