- hot spots are clickable screen areas (e.g. in menus and prompts) that   generate key-strokes
- commands may be from 1 to 127 ASCII-characters in length
- currently using the X10 mouse reporting mode, may change
- all mnemonics strings (~Example) are automatically hot-spots
- The new ~ @-code defines a hot spot
- Any screen-clear operation clears all hot spots
- sbbs now tracks the current screen (cursor position) row
- eliminated the old "tos" (top-of-screen) boolean (row == 0 indicates "tos")
- created an sbbs_t::ungetstr() method
- keep track if in pause (hit a key) prompt, for special mouse behavior

new JS console object:
- row property
- tos property is now read-only (and deprecated)
- new methods:
  add_hotspot()
  clear_hotspots()
  scroll_hotspots()

redrwstr() gets some UTF8 touch-ups as part of this commit. <shrug>

- Export all FIDOCTRL (other FTN kludge lines) to the QWK HEADERS.DAT file.
  These should already be imported if they exist, but were never added during
  export, so untested/new behavior. The control paragraph (kludge line) of
  specific interest here is the "CHRS" (charset) kludge we need for UTF-8.

- Don't use the QWK "newline" character (0xE3) when the message is UTF-8.
  Use bare-LF's instead. This is pretty untested at this point as I will need
  another QWKnet board to post or receive UTF-8 encoded messages to test,
  getting the code into CVS is the first step. At least for now, there's no
  opt-in/out for this behavior. If your BBS has UTF-8 encoded messages, some
  QWK nodes or offline readers may have trouble with packets which include
  those messages. Or they may work fine (but likely display garbage CP437
  chars in-place of the proper Unicode codepoint glyph).

- The beginning of UTF-8 input support in getstr() - which needs more work,
  particularly around character and word deletion and insertion.
- The internal message editor now supports UTF-8 messages and kind of somewhat
  supports inputting UTF-8 characters in message text.

New put/print text flag: P_AUTO_UTF8 which can auto-detect UTF8 strings and
do the "right thing" for the user's terminal. New associated sbbs_t method:
auto_utf8() which automatically sets P_UTF8 for any stirng that begins with
a UTF-8 BOM (ZWNBSP). Else, if the P_AUTO_UTF8 mode flag is set, then
it checks to see if the string contains invalid US-ASCII chars but valid UTF-8
sequences and then sets P_UTF8 accordingly. Used by putmsg() and bputs().

There's a new permuation of bprintf() which accepts a mode argument
(i.e. for P_UTF8) and passes it on to the new mode-capable bputs().

sbbs::lputs() will log the current user alias already, logline()->lputs() would
create log messages with the user alias twice.

from the Chat menu would immediately clear the screen and redisplay the
menu after displaying the change in the node's state. This was due to the
enhancement in rev 1.77 of con_out.cpp whereby we no longer increment
lncntr if the first lines displayed after a key-press are blank (who
cares if blank lines scroll off the screen?). That's fine and all, but the
auto-pause check in outchar(FF) would only auto-pause if the line-counter
was greater than *one* (has been this way since forever). So with the
enhancement in 1.77, a single non-blank line displayed after a key-press
was now not enough to trigger the auto-pause ([Hit a Key] prompt).
So I've changed the line-counter trigger value to greater than *zero*,
which means we could have some new excessive auto-pauses, but other places
where auto-pause wasn't working, should again.

One new excessive auto-pause was after the system password was entered at
the SY: prompt, so that fix is included in this commit.

or more have elapsed since the last system password (SY:) prompt. Similar
to Linux 'sudo' command. Might make this time configurable rather than
hard-coded at some point, but 15 minutes seems like a good default.

password string.

bbs.login() now accepts 2 additional optional arguments: user_pw and sys_pw
if these passwords are supplied, they won't be prompted for by the underlying C
functions. If the password_prompt argument (2nd arg) is not supplied, no prompt
will be displayed, but a password must still be entered.
The default behavior is the same as before.

Added HOST and IP keywords to allow restricted access/privileges to/for
specific remote hostnames or IP addresses (wildcards allowed).
All string-argument type ARS keywords (e.g. SHELL, PROT, etc.) now support .can
style wildcards.
The current remote client is now used for protocol, host, and IP ARS checking,
when available, so this requires passing the client pointer around (which
explains why so many files are touched by this change) and takes care of a
long standing to-do item (the user's 'modem' value was used for the PROT
value checking, which was not always correct).

console mode.

Simplify redrwstr() by combining ANSI/non-ANSI terminal support.

by properly const-ifying the appropriate functions and variables.

Not yet tested on Win32

- returns true/false if the user's terminal supports all the passed flags
- returns the supported flags if no flags are passed for comparison
- automatically uses the auto-terminal-type flags if no user is logged-on

con_hi.cpp to str_util.c.
strip_invalid_attr now supports strings up to 1K in length.

No longer logs (or displays locally) failed password attempts if the sysop has so configured the system in SCFG.