*This* is the way. Oops.

This is the way.

The alternative is to explicitly copy/paste the type everywhere
forcing the compiler to do the only thing it could possibly do,
and making it painful to change a type later.

Honestly, in my opinion, these warnings should just be disabled
completely everywhere.

Found by MSVC

Just use the raw value and a comment.

If DL was passed a parameter equal to or greater than the number of
lines from the current line to the last line in the region, it would
try to move a negative-sized box up, which resulted in a crash.

This fixes that three ways:
1) Do not allow moving boxes with negative X/Y sizes
2) In dellines, clamp the lines to the number that could be deleted
3) Don't move lines up of all rest of the lines are being deleted

This should be made palette-aware as well, but since the current
consumer doesn't modify the palette, it's good enough for now.

Previously, we compiled in a RGB -> YCbCr table and used that for
scaling, which added 128MB to the size of binaries that enabled
non-integer scaling.  The decision was then made to eliminated
non-integer scaling support from the Synchronet utilities to save
disk space.

With the use of the YCoCg-R, we can more efficiently transform between
the colour spaces, (about 50% more CPU than using the table), so
it's no longer prohibitive to do this in real-time.

This should also have the effect of making the Synchronet utilities
use the correct aspect ratio for the various screen modes rather
than forcing the use of square pixels.  I expect DigitalMan will
hate that.

It seems to provide similar perceptual results, and is much faster
to transform with RGB.  It's still slower than the table lookup,
but not crushingly so.

Still using BOOL where we need Win32 API compatibility.
Using JSBool instead of BOOL or bool where it matters.
Changed most relevant TRUE/FALSE to true/false too (though it's not as critical).

You shouldn't need to #include <stdbool.h> anywhere now - gen_defs.h should do that automatically/correctly based on the language/version/tool. In C23, stdbool.h isn't even needed for bool/true/false definitions (they're keywords), so we don't bother including stdbool.h in that case.
Microsoft didn't define __STDC_VERSION__ in their older tool chains (even though they were C99 compatible and had stdbool.h), so we use a _MSC_VER check to know that there's a stdbool.h we should use in that case.

For other/old compilers (e.g. Borland C) we #define bool/true/false following the pattern of stdbool.h (doesn't use a typedef).

I didn't convert UIFC yet.

This addresses issue #698

... to disable the OS or Window Manager's "close" app icon/control/option
which attempts an ungraceful termination of UIFC apps (e.g. SCFG) and does
weird and wonderful things (e.g. infinite loops which are invisible on
Win32-GDI, so you end up with a ghost/zombie process).

Disabling the OS/WM close option is an alternative solution to checking
uifc.exit_flags & UIFC_XF_QUIT everywhere you need to to avoid a
looping/zombie process.

Next up X11, which appears I need to remove _NET_WM_ACTION_CLOSE
from the _NET_WM_ALLOWED_ACTIONS Atom... ?

64 is not ASCII C, and it does not respond as @Term.

With 0xE0 being used for ciolib "super-extended scancodes", a literal
0xe0 can't pass through the input path.  This is an issue in CP866 (р)
and KOI8-U (Ю) as well as CP437 α.

Should fix SyncTERM SF bug 123.

For waveOutOpen and friend functions

.. so it can be loaded in the same solution as the conio project

to differentiate it from the non-SDL version of the conio property sheet

This allows directly setting bright foreground and background colours
rather than using bold and blink to indirectly modify them.

These do not have an effect if the desired mode is not possible
(ie: no bright background, no bright foreground).