The flags should always be empty anyway.

This makes sure the compiler doesn't complain about problems in those
files.

It's only the -Werror part we want to be conditional on being debug
builds.

This was not meant to be included in the previous commit. The static
storage for the font string is more than enough.

Fl::set_font() doesn't keep its own copy, so we need to make sure the
font string doesn't get freed or overwritten at a later point.

CentOS Stream isn't fully compatible with RHEL, and there are no useful
RHEL images available, so that leaves us with one of the new RHEL forks.

Add support for RSA-AES security types (Java version)

Use the font specified by the system for UI elements. For Windows and
macOS this is straight forward, but Linux is more complex as there is no
single source for this information.

Try to follow the actual padding that FLTK adds to these widgets.

The extra one pixel on each is because of a bug in FLTK's focus drawing
code, where the box is always one pixel too small in both dimensions.

This is how GNOME does things, so let's do the same so things look
similar.

To conform with how e.g. GNOME sets its margins.

This makes the code much cleaner, and easier to update.

Makes it easier to adjust the UI from a central place.

Makes it easier to adjust the UI from a central place.

Outlines are no longer commonly used. Instead visually separated
headlines are the norm.

Classical tabs are very dated. They are also a practical problem as you
get very limited in the numbers of tabs we can have, and how long the
text can be on them.

Switch to one popular modern model with a list on the left instead where
pages can be selected.

If the translations change then these files need to be regenerated as
they include data from those.

It's just the name of the system, so there is nothing in that string to
translate.

This should be happening implicitly, but isn't always for some reason on
macOS 13.

The system steals keyboard events for certain system keyboard shortcuts,
e.g. Cmd+Tab. Unfortunately this isn't considered a focus loss, so we
don't realise we've lost a few keyboard events and can end up in a
confused state.

Fortunately it is possible to detect when this happens and reset the
keyboard state, just like we do when focus is lost.

Delay startup of VNC sessions until user databases are up and running.
This is the same ordering that GDM imposes to make sure users can
actually log in.

We might often fail to find a matching X11 keycode when the client has
a different keyboard layout and end up with no key event. To avoid a
failure we add it as a new keysym/keycode pair so the next time a keysym
from the client that is unknown to the server is send, we will find a
match and proceed with key event. This is same behavior used in Xvnc or
x11vnc, although Xvnc has more advanced mapping from keysym to keycode.

We don't want any stray exceptions as we are cleaning up, so handle any
still pending decoder errors by just logging them. We are already
shutting down so there is no need to abort the connection here.

They don't get access bits until they've been authenticated, so avoid
doing any checks on clients in those early states.

It probably wanted to say "newer", but let's say "later" instead. Other
building requirements say "later".

Avoid having to update this manually.

These require a key to have been set up on the server beforehand, so
they do not give a good default experience as clients will be unable to
connect.

This is missing in the CentOS 9 repositories for some reason. Download
it directly from the build system until this can be fixed.