This utility is for manual testing, not automated testing, so there's
no point in anyone building it as a side-effect.

Removing it should also flatten the dependency tree and allow more
parallel jobs (there's up to 18 seconds to gain!)

It didn't work anyway.

In T2B (top to bottom centering) mode, the 'top' parametr value isn't actually
for the top of the window position (later), so just zero it here in case it
was specified (and non-zero) to correct the calcutation on the next lines:
```
	if(top+height>s_bottom)
		height=(s_bottom)-top;
```

This should ensure that once quit is used, everything exits, but
apparently, this never worked.

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.

... declared with attribute ‘warn_unused_result’

Mostly (all?) about unchecked return values. Unexpected failures to read or
write some files could've definitely led to some weird bugs.

The sketchiest bit here is removing the uifc -> conio dependency
which, since it needs to depend on conio_sdl now means if something
is relying on that, it will need an explicity dependency...

We'll see what the pipeline says.

Maximize screen realestate for options/settings display:
- Don't place a margin around windows when in a narrow screen mode.
- Don't display shadows on windows when in a narrow screen mode.

This commit also fixes a bug in uinput() when left was non-zero and the total
width (left + width) would be too wide for the screen. This bug was apparent in
SCFG->Message Areas in 50 column mode (no Message Group window would be
displayed when a message group was selected).

The the date/time display would overwrite parts of the application
title in narrower screen modes, so let's not do that.

While we're here, eliminate some explicit int64_t usage.

(not sure why uifc_winmode_t is signed since it's a bitfield, but
that's above my pay grade).

When running Windows 11 in a VirtualBox VM, Sleep(1) appears to take
much more than 1ms to return.  This causes large delays drawing menus
using WIN_DYN (as SyncTERM does).

If WIN_DYN is set, just use kbhit() with no delay.  Leave the delay
there for !WIN_DYN though.

This should generally speed up SyncTERM menu navigation as there
was a 50ms delay for each menu on the screen.

Sometimes F1 doesn't work, Ctrl-Z isn't documented, but there is a '?' displayed
when help is available, so it's reasonable to assume someone might try/use it.

warning: ‘%s’ directive writing up to 16384 bytes into a region of size
between 1 and 16385 [-Wformat-overflow=]

Running 'scfg -id -w' would crash due to NULL pointer dereference and display
prompts with a "[(null)]" title. Fixed.

e.g. this a way to set the K_TRIM mode globally for all keyboard input

K_TRIM causes leading and trailing whitespace to be trimmed.
K_NOSPACE disallows any whitespace characters to be added to the string.

Previously, trailing whitespace was always trimmed. Now, only do that
if/when K_TRIM is specified.

I'm not sure what was going on with this addition of 6 when mouse is enabled (and didn't check for WIN_DYN flag set!), but is wrong. And we need to add 4 to the title_len when figuring out the centered-offset.

... but not for GCC or Clang interestingly enough.

The title isn't displayed in this mode, so the title length is 0.

Why is title being strdup()'d here? Something to look into.

Fixes SyncTERM SF bug 93

Before this change, dynamic parent windows wouldn't be redrawn as
active after showbuf() returns.

Passing either WIN_LEFTKEY or WIN_RIGHTKEY in the window "mode" argument enables this new indicator in the upper right of "list" windows. These indicator arrows are mouse-clickable too (translate to the left and right arrow keys).

We had defined uses for all 32 available WIN_* mode bits, so I extended the win mode type from 32 to 64 bits (should this now be called uifc64.c?) :-)

Anyway, it'll be easier to add more WIN_* mode flags as needed later, but I do wonder about JavaScript support (not so great for > 31-bit integers).

Oddly enough the hbuf wasn't actually modified.