Pierre Ossman [Fri, 14 Jul 2023 11:10:27 +0000 (13:10 +0200)]
Workaround for broken fl_arc()/fl_pie()
There is something broken with these FLTK draw routines on Windows. They
leave gaps at the start and end of the arc/pie rather than filling the
whole specified span. So we need to nudge the numbers a bit to work
around this.
Pierre Ossman [Fri, 14 Jul 2023 08:08:25 +0000 (10:08 +0200)]
Apply custom theme to FLTK
Inspired by modern Windows appearance, and to some extent macOS. They
have flat boxes and use white, or very light, colors for interactive
elements. Unfortunately we can't directly control the colors of
widgets, so instead we just lighten everything that uses this box type.
GNOME uses a different design, both their older and newer style. But UI
look is less consistent on Linux, so hopefully our new look is decent
enough there as well.
Pierre Ossman [Wed, 5 Jul 2023 14:23:58 +0000 (16:23 +0200)]
Unbreak -Wformat warnings when gettext is used
gettext replaces all *printf() functions on platforms that don't fully
conform to the POSIX behaviour. Unfortunately, gettext fails to tag
these replacement functions properly so that -Wformat can still do its
thing.
Resolve this by adding a redudant declaration of the relevant functions,
with the attribute tagging in place.
Pierre Ossman [Wed, 5 Jul 2023 14:22:35 +0000 (16:22 +0200)]
Use smaller, stable, int for history index
The size of size_t depends on the architecture, so we need to have
different conversion to and from strings. But we don't really need that
range, so avoid the issue by using a standard integer size.
Pierre Ossman [Wed, 5 Jul 2023 08:22:42 +0000 (10:22 +0200)]
Make sure we handle all certificate issues
We don't want to proceed unless we've made sure the user has approved
the issues with the certificate. So add an extra check that all status
flags have been dealt with.
Pierre Ossman [Sat, 18 Mar 2023 13:59:27 +0000 (14:59 +0100)]
Don't allow surrugate code points in UTF-8
These are not valid outside of UTF-16 so seeing them in a UTF-8 sequence
means that something is wrong with that sequence. Best to filter them
out rather than letting them propagate and have unknown effects.
Pierre Ossman [Sat, 18 Mar 2023 12:53:26 +0000 (13:53 +0100)]
Clean up string encoding handling
We should handle this in the low-level protocol code as much as possible
to avoid mistakes. This way the rest of the code can assume that strings
are always UTF-8 with \n line endings.
Pierre Ossman [Wed, 21 Jun 2023 11:58:57 +0000 (13:58 +0200)]
Move where -nodefaultlibs is specified
The previous method isn't compatible with CMake's try_compile() as it
will respect CMAKE_EXE_LINKER_FLAGS, but not CMAKE_C_LINK_EXECUTABLE and
friends. This results in the default libraries being completely missing,
and the compile test failing.
Pierre Ossman [Wed, 8 Mar 2023 17:15:33 +0000 (18:15 +0100)]
Detect leaving window on zaphod systems
The coordinates we get are relative the root window of each screen, so
we can only trust them if we are on the same screen. So let's explicitly
check that we are still getting events from the expected screen by
checking the root window field of the event.
Pierre Ossman [Tue, 28 Feb 2023 15:00:15 +0000 (16:00 +0100)]
Throw exception instead on bad access check
An assert will kill the entire server, which is overly harsh when there
is a problem with a single connection. Instead, throw an exception which
will just disconnect that specific client.
Mark Mielke [Mon, 20 Feb 2023 05:38:52 +0000 (00:38 -0500)]
VNCSConnectionST clipboard functions should check state before access.
Clipboard functions may run on connections that are not yet at
RFBSTATE_NORMAL. Due to recent hardening of the accessCheck() function,
it is important to validate that the state is RFBSTATE_NORMAL before
calling accessCheck().
Pierre Ossman [Thu, 12 Jan 2023 06:58:18 +0000 (07:58 +0100)]
Warn if Point/Rect/Region methods are used wrong
It is easy to get confused if these methods modify the existing object,
or return a new one. So let's mark the return value as critical so the
compiler can help out if someone gets it wrong.
Pierre Ossman [Sun, 20 Nov 2022 12:25:23 +0000 (13:25 +0100)]
Avoid redefining errno
This can have unexpected consequences as some code may rely on it being
a simple variable. Instead to what we do in Socket, which is to define a
unique name for getting socket error numbers.
Pierre Ossman [Wed, 11 Jan 2023 16:21:56 +0000 (17:21 +0100)]
Make strSplit() simpler and safer
Get rid of all the magical re-allocation and shuffling and instead just
return a new set of strings that is fully splitted. Will consume a bit
more memory, but is a lot safer to use as there is less confusion about
ownership of memory.
Pierre Ossman [Tue, 10 Jan 2023 13:30:37 +0000 (14:30 +0100)]
Return std::string instead of dynamic allocations
We mostly use classical C strings, but the memory management around them
can get confusing and error prone. Let's use std::string for the cases
where we need to return a newly allocated string.
Pierre Ossman [Fri, 13 Jan 2023 10:15:36 +0000 (11:15 +0100)]
Better fallback for missing peer address
A blank string might be very confusing, depending on where this will be
used. Let's give something more visible back in the cases where we
cannot get the proper name for the peer.
Pierre Ossman [Wed, 16 Nov 2022 06:55:03 +0000 (07:55 +0100)]
Include other targets in .la files
We have internal dependencies that should be respected, as otherwise it
will be up to the user of the .la file to figure out the correct order
of the libraries.