This means ciolib utilities built with MSVC won't have the right
manifest information, but the documentation is terrible and I can't
figure it out.

Looks like this was where it messed up first.

It appears they just set the default values, so try that out.

Presumably, "something" is setting it earlier so it can't be set
again because reasons.  To work around this, add a manifest to
ciolib library that asserts the binary is DPI aware and requests
Windows not do GDI scaling.

Not sure if manifest .o files in a lib are linked in by things, but
SyncTERM pulls the .o out and explicitly links it, so this should
fix SyncTERM at least.

We will now try SetProcessDpiAwarenessContext() first, then
SetProcessDpiAwareness() second, and finally SetProcessDPIAware() [sic].

Also, "handle" the WM_DPICHANGED event.

This may solve problems initializing SyncTERM on systems with two
displays that have different DPI settings.

SlyEdit: Update for the isPrintableChar() function to allow more for UTF-8 (it's a simplistic function).  Also updated the version number in slyedcfg.js.

See merge request !411

SlyEdit: Update for the isPrintableChar() function to allow more for UTF-8 (it's a simplistic function).  Also updated the version number in slyedcfg.js.

This allows easy copy/paste without scrollback hacks on BBSs that
insist on taking over the mouse just so you can move the mouse and
click a character rather than press one key because it's 3l337..

When using $^, all the auto-dependencies are included in the link
command-line, which includes sbj.c and all the .h files, causing
the link to fail if dependencies exist.

This won't matter now since only one thread ever touches it, but
when cool stuff happens, it could.

This allows ALT-B from dialing directory to show the last seen
thing, not the extra blank screen added to the end.

Doesn't fix anything, but a huge QoL improvement for people who use
ALT-B after disconnecting.

Fixes issue 124 on Sourceforge.

The column-width of UNICODE 'zero-width' character is now autodetected. This
property allows one to use/change this autodetected width (normally 0 or 1).

DDMsgReader: When checking the user's external editor settings, make sure they actually have an external editor configured, or else DDMsgReader will error out.

See merge request !410

DDMsgReader: When checking the user's external editor settings, make sure they actually have an external editor configured, or else DDMsgReader will error out.

xtrn.ini: For SlyEdit, the "Support UTF-8 Encoding" is now Yes.  Also, updated the ARS to "ANSI AND COLS 80"

See merge request !408

Eric Oulashin authored 1 year ago and Rob Swindell committed 1 year ago

xtrn.ini: For SlyEdit, the "Support UTF-8 Encoding" is now Yes.  Also, updated the ARS to "ANSI AND COLS 80"

SlyEdit: Header display update for UTF-8.  Added 'add graphic char' to DCT menu.

See merge request !407

Reduces the time after a forced hangup that you need to wait before
returning to the main menu.

at least three times since we enabled the test suite.  The odds
of that happening *should* be one in a million, but NetBSD managed
to fail this time (don't remember previous times, and not sure
how to find them).

For now, I'll just change this so there's a one in a trillion chance.

This shouldn't be necessary, but Coverity thinks it's a good idea,
and it's simple enough to do without hurting anything.

do math to get there.

A couple were actually serious, most were unimportant.

Except on Borland, which presumably doesn't have strtoull().

Don't corrupt UTF-8 strings with SAFECOPY() (use new SAFECOPY_UTF8).

Some terminals (notably, Windows Terminal) display zero width UNICODE chars
as a single column-wide space. <sigh> Auto-detect the zero-width "width"
(1 or 0) of the terminal during connection and UTF-8 auto-detection.

getstr() works a lot better now with UTF-8 strings with wide chars (e.g.
emojis), but likely much more to do.