hour in the future. This allows for small adjustments in the local system clock.

the renderer.  Fixes crash when there's fewer screen pixels than in the
window.

This allows the saved scaling to work again, and makes the mouse not weird
when scaling is secretly set differently.

Previously, an atexit() function could call exit() (for non-SyncTERM utils)
causing the program to occasionally crash rather than exit cleanly.

- that's not nice.

when such a size is selected.

META-<arrow> keys now change the window size in SDL mode... left and up
make the window smaller, and down and right make it larger.

On Windows, the META key is the Windows key... On Apple systems, maybe it's
the Apple key?  *shrug*

This allows Lt. Blue on Blue for C64, Green on bright black for C128 40 col,
and Light grey on black for C128.
Commodore modes are no longer capable of blinking, which I believe is accurate.

Remove CIOLIB_MODE_SDL_YUV* macros, these modes have no point anymore
Fix SDL prototypes

Use _beginthread() instead of SDL_CreateThread().  For some reason, using
CreateThread() sometimes caused an application crash (ie: when using -?)
Everyhing else uses _beginthread() so there's no reason for this to be
special, especially when it breaks stuff.

Win32 now (and it only runs main() from WinMain()).  This shouldn't be
necessary for MSVC builds.

load_sdl_funcs() is no longer called from SDL_win32_main()
Further, the Handle thing doesn't exist anymore, so just remove it.

It's not unlikely that any utilities using SDL will have new issues... you
may want to hold off on updates for a bit until this settles unless you
don't use SDL mode.

- min_password_length (currently hard-coded to 4)
- max_password_length (currently hard-coded to 40)

Remove 2 unused system properties (nobody uses PostLink/UTI drivers any more):
- psname
- psnum

(should default to current behavior: Yes). Set to No to not require the system
password while logging in as a system operator (level >= 90). The system
password will be required while logged-on and performing administrative-like
operations.
Added by request from Altere.

Also a little code clean-up: replacing repeated constants with uifcYesNoOpts.

(should default to current behavior: Yes). Set to No to not require the system
password while logging in as a system operator (level >= 90). The system
password will be required while logged-on and performing administrative-like
operations.
Added by request from Altere.

adding 'int' to a string does not append to the string

address of array 'this->cfg.textsec_mod' will always evaluate to 'true'

message areas. If not specified, the address from the template sub will be used
(if there is one), else the first specified system FTN AKA is used (as before).
Removed a bunch of superfluous carriage-returns.
Use the Copyright notice defined in sbbsdefs.h.

Added more user flag definitions (not currently used here).

in the text.dat. This may be a sysop-configurable value in the future.
text.dat NewPasword is now NewPassswordPromptFmt and includes both the
minimum and maximum password length as % specifiers.

when echo is disabled or when we're echoing X's (for password input).
Ctrl-R key would redraw the raw password at a password prompt, even when the
console is in Echo-X mode, pass a non-zero mode flag to redrwstr() to fix that.
Also, some experimental UTF-8 input stuff that doesn't work right yet.

specially, just pass them on to the script as-is. Included a JSDOC note about
the use of js.exec.apply() to pass a variable number of arguments (ala execv).

Thanks Tracker1 for the pointer to 'spread' which led me to function.apply()
and the JS-standard method of achieving the result I needed with this
enhancement.

I still think that a script that calls exit() is unlikely to expect non-string
arguments in the first place, but if we don't need special case behavior, it's
better not to add it and keep the behavior consistent with load() and
require(). That was the decision of the executive board anyway. :-|

patch/bug-report by Mark Lewis.

use this in place of system.node_list[] if you're going to be using a lot of
the properties and passing them around to methods which are going to each
possibly dereference the values, as *each* deference results in a read of the
node record in the node.dab. On my system, a simple node list (e.g. /L
command) would result in between 60 and 100 reads of the node.dab (for a 13
node system), which was nuts.

The system.get_node() method currently leaves the node record unlocked and
there is currently no equivalent put_node() method, so you still need to use
the system.node_list[] for modification of node records. But, I now see there
are race conditions with the current methods of read-modify-writes of the
node_list[] properties. We should be locking a node.dab record, reading it,
modifying it, writing it, and then unlocking it - as is done in the C/C++
code. So... that's a todo item.

Also created system.stats.node_gets to track the number of node.dab reads
from a single instance of the system object. May remove this any time.

script are arrays, pass each element of the array as a separate argument to the
child script. This allows one script to generate a variable-length list of
arguments to be passed to another.

Improve "script missing" error reporting in js.exec().

not v3.16.

This is an artifact from SBBS v2 for DOS:
The file would contain the address of a shadow of the modem status register
(written by execdos.exe) for dropped-carrier detection in xsdk doors (or the
"dcdwatch" utility) while the BBS was "shrunk" out of memory to execute the
external program with maximal available memory.