Updated the logic for following a message's thread_back/thread_next & thread_id matching (using the ( and ) keys): Now first checks to see if thread_id is available (it checks to see if running Synchronet 3.16 and thread_id exists in the headers), and uses thread_id if available; if thread_id is not available, then it falls back on using the thread_back & thread_next fields.

Added by-title, by-author, and by to-user thread navigation as in Synchronet's stock message reader.  Also, added the ability to change to another message sub-board from the message list (using the C key).  Note that the ability to change to another sub-board is not enabled when doing a newscan or new-to-you message scan, since a scan is a more controlled flow.

for sbbs_t::loadposts().

- thread forward and backward by thread-id (, and .)
- list your unread messages (U)
- list new messages (N)

Removed extra smb_freemsgmem() stuff in listmsgs() loop (leftover?).

Fixed the name of the YNQP text.dat item.

scanposts(), and listsub(). These functions are exposed in the JS 'bbs' object
as scan_subs(), scan_msgs(), and list_msgs().

scanposts(), and listsub(). These functions are exposed in the JS 'bbs' object
as scan_subs(), scan_msgs(), and list_msgs().
Wherease previously, all of "your messages" (messages addressed to you)
would be found/displayed if the user answered (Y)es to the "Subjects Only?"
prompt, and only un-read message (to you) would be displayed if they answered
(N)o to the "Subjects Only?", providing long-standing confusion about the
different behavior, now the user is prompted whether to display un-read
messages only (in scansubs/scanallsubs), and in the case of the logon
question to "Search all subs for un-read messages to you?", only un-read
messages are listed/displayed, regardless of how the user answers the
"Subjects Only?" question.
SCAN_UNREAD is only applicable when combined with SCAN_TOYOU.

Added new commands to the msg reading prompt: 'N' (list new messages), 'U'
list un-read messages to-you.

2 new text.dat entries: DisplayUnreadMessagesOnlyQ and NoMessagesFound

getusrsub() returned the completely wrong sub-board number. It assumed that
getusrgrp() returned a 0-based index when in fact it returns a 1-based group
number. This bug was only visible when using certain @-codes (e.g. "SN",
"SL", "SR", and "SMB_SUB_NUM") when a sub-board was open via Synchronet
internal function (i.e. not via JS MsgBase class). If the current group was the
last group visible to the user, this would cause a crash.

Thanks!

than the built-in logic, if Ctrl-C abort status was already active, it would
still prompt for a key rather than immediately returning a negative/No result.

a buttload of data.  If the input queue filled up before the socket was closed,
the input queue could be stuck waiting for the ring buffer to drain while
conn_close() is stuck waiting for the input thread to stop.

We now consume data from the input buffer while waiting for the input thread
to stop.

SlyEdit v1.44 update - Bug fix: When cross-posting a message in other message areas, the message area settings are now checked to see whether the user's real name should be used for the 'From' name.  Previously, SlyEdit was always using the user's alias as the 'From' name when cross-posting.

and release it last.

if you have valid SAUCE data in the file.

Not *really* tested, only checked that it didn't break mah lemons.

Added scripts (and information in the Read Me file) for setting up Digital Distortion Message Reader in the new Loadable Modules options in SCFG > System > Loadable Modules.  This enables Digital Distortion Message Reader to be used, for instance, for reading personal email or doing a message newscan during the login process.

Changed the traditional/lightbar help color text to cyan.  I had accidentally left it as brown (dark yellow), which I was using during testing.

hold the lock.  This should finally fix all the things I hope.

already held by the bitmap layer.

This fixes the Linux crash on exit in SDL when X11 mode is used (and possible
others).

a potential problem with grabbing vstatlock).  Call XCloseDisplay and terminate
the X11 event thread on exit().

This still does not prevent the crash on exit for Linux.  This appears to be
an issue with SDL.

setup_surfaces() was never called for overlay mode, resulting in the window
contents never changing size.

scaling but forces it to 2.  This is to allow two "pixels" for each "real pixel".

If we don't have two pixels, the chrominance values cannot be represented
correctly, only the luminance... resulting in a monochrome image.

JS model (bbs.scan_msgs() method).

was never used. This was intended to be a method for internationalization,
letting the sysop change which key is used as the uiniversal "quit" key.
This commit replaces most of the uses of the hard-coded 'Q' for quit wtih the
3rd charcter in the text.dat YNQP string. Some hard-coded menus still have the
'Q' key hard-coded and will need to be addressed later. The text.h YN index
macro was changed to YNQP and the JS text index variable name will change
as well.

draw the top line and first left vertical row in a file list box.  The rest
of the box was drawn in whatever attribute text.dat left it in.

Valgrind report).

Optionally, external modules may be executed in place of "built-in" operations
for:
- reading mail (email or netmail)
- scanning posts (searching/scanning/reading a single sub-board)
- scanning sub-boards (all, one, or a group)

Each of these may be configured (in SCFG->System->Loadable Modules)
with command-line options for a total length of up to 63 characters.

Note to module programmers: each module here will be passed additional
command-line arguments to indicate how or why the user operation was invoked.

For the Reading Mail module, the 'which' value (in decimal) and the user-number
is passed (in decimal). Usually the user-number will be the current user logged
in, but not always (e.g. if the user is a sysop and reading other user's mail).
The 'which' values (defined in load/sbbsdefs.js) of MAIL_YOUR, MAIL_SENT,
and MAIL_ALL must be handled (MAIL_ANY won't be used).

For the Scan Posts module, the sub-board number and scan mode (both in decimal)
and the 'find' string (text being searched for) are passed as arguments
(in that order). The scan mode values (defined in sbbsdefs.js) are the same as
those supported by bbs.scan_posts(). All of the values should be supported
and they can be combined (e.g. SCAN_CONST|SCAN_NEW
and SCAN_NEW|SCAN_TOYOU). The 'find' string is only used if the SCAN_FIND mode
bit is set. It is the responsibilty of the module (if configured) to enforce
sub-board read access restrictions.

For the Scan Subs module, the first argument is 1 if "all subs" are being
scanned, 0 otherwise (normally the user is prompted for the breadth of the
scan in this case, but that's up to the module author), and the scan 'mode' is
passed in decimal, in that order. If the SCAN_FIND mode flag is passed in, this
module should prompt the user for the text string to search for. If this module
is not configured, the Scan Posts module will be executed for each sub-board
scanned.

Recursion protection was added, so it is actually possible for the Read Mail
module, for example, to call bbs.read_mail() and it'll work, but why would you?

If any of these user operations are initiated during logon, at the request of
Baja or JavaScript module, or whatever, and if the module is actually
configured (and not already executing to handle the operation), the module
will be executed in-place-of the built-in functionality. Feedback welcome,