- 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>

A double-click of the mouse button now selects an item on the menu if multi-select is enabled.  A double-click is detected if 2 mouse clicks happen within 0.4 seconds (arbitrarily chosen).

for sysops and a pain. Specifying "-r HEAD" does not actually pin the files
to the latest, but rather pings them to the latest rev *at that time*, which
makes subsequent cvs-updates a pain.

corresponding *_net_addr field is present (not NULL).

Don't strip the "user@" portion of a *NETADDR header field if the specified net-type is NET_NONE.

Allow an added or modified message header to have to/from/reply-to "net type" values of NET_NONE. This is a weird scenario, but it is technically possible (e.g. for nntpservice.js) to save a message with a to/from/treply-to "net address" header, but an associated net-type of NET_NONE. By saving the net-type NET_NONE, when saving a modified header, if the associated net address header field value cannot be parsed into a valid network address, there won't be any error reported, e.g.
Error -110 adding SENDERNETADDR field to message header

Now includes mouse support.  A mouse click on an item in the menu will make it the currently highlighted item, and if the scrollbar is enabled, clicking above/below the solid scroll block will do a page up/down.
I'm wondering if there's a function (other than time()) that has higher resolution than 1 second (perhaps milliseconds?) so I can detect a double-click in a short amount of time (to perhaps add an item when multi-select is enabled).
I also saw the 'motion' variable, and I'm wondering if that coudl be used to detect mouse motion when the button is pressed (so that the menu can scroll when the mouse is moved while the mouse button is pressed over the scroll block).

warning: iteration 9 invokes undefined behavior

events.

and the scrolling of the things.

Convert relative "dir" values from json-service.ini to absolute paths to resolve crazy errors that can transpire if you have an xtrn/xtrn/<game> directory in addition to xtrn/<game> directory.

Currently this only has a 'line' property, being which line from the
source document was clicked.
It may later become useful to report which position in the original
string was clicked, or what word, etc.

Now uses KEY_PAGEUP and KEY_PAGEDN, as defined by key_defs.js rather than using its own pageup/pagedown variable definitions as it was doing before.  Also, fixed some weirdness & improved the apperance when selecting & de-selecting items in multi-select mode when using color arrays to color the items.

(post word-wrap) to a line from the source document/array.
Added mouse support to getcmd (scrolling, left click).
If it returns a number, that's the line (from the original document)
that was clicked. This needs some enhancement.

Automatically detect the character set of QWK-imported messages (that don't already have a FidoNet "CHRS" header) and create/set the FIDOCHARS header field accordingly (UTF-8, ASCII, or CP437). This should resolve the issue I observed of QWK-posted messages on FidoNet with the wrong CHRS header value (i.e. CP437, when the message body in fact contained UTF-8).

Some echolists (e.g. linuxnet.na) use '%' for comments (rather than ';') so just ignore any lines in imported echolists that begin with a non-alpha-numeric character.

*always* set the KILLSENT attribute flag on email/netmail received for relay via SMTP (regardless of the Internet/Fido netmail setting in SCFG).
The sender should already have a copy (e.g. in their outbox), if they want to keep it.

Was making my command shell do wacky things.

MSG_SENT is in the netattr field, not the attr field. Double-oops. Thanks Dan_C and Nelgin for bringing to my attention.

Got rid of globals.
Added mouse support for menu, quit, and bulletin scrolling.

of othat displayed warning about using default value of /sbbs/ctrl.