For cross-posting, to make sure the user can post in a sub-board, SlyEdit now checks the can_post property of the sub-board rather than checking the ARS.  The can_post property covers more cases (such as whether the sub-board is a networked sub and the user has the N restriction).

Incremented the version to 1.72 and date to 2020-03-04 to be up to date with today's release of SlyEdit.

Added support for a new option in SlyEdit.cfg: allowSpellCheck, which specifies whether or not the spell check feature is allowed. Valid values are true and false; it defaults to true if not specified.  You might want to disable spell check if, for instance, the spell check feature causes an "out of memory" error on your system.

New configuration option: allowSpellCheck.  This specifies whether the spell check feature is allowed or not.  It defaults to true if not specified.  You might want to disable spell check if, for instance, the spell check feature causes an "out of memory" error on your system.

Re-indented some functions to be more consistent with other code in SlyEdit.  No change in behavior.

The postMsgToSubBoard() function now checks to ensure the user has posting access to the sub-board before posting the message.  For cross-posting, SlyEdit already does not allow the user to select sub-boards they can't post in, but I figured it wouldn't hurt to have this function check for that before posting the message.

Install with "jsexec msglist -install"
Further sysop documentation and help files are forthcoming.
Requires latest and greatest sbbs v3.17c (dev build) for full functionality.

now accept an optional print-mode (a.k.a. pmode) argument to provide more
control over the printing that happens in these functions/methods.
The immediate use is for P_NOCRLF to stop the newline from being printed
after a yes or no response (e.g. in a full-screen UI), but there could be other
uses.

Could sear I'd already done this.

checking for non-NULL value.

to an object with JSVAL_TO_OBJECT(). Go figure.

JS) which will be executed when a users uses the the (L)ist msgs command from
the "Reading" sub or "Reading E-mail" prompt.
The arguments passed to the module are: <sub-code> [which]  [usernum]  [lm_mode]
The additional optional arguments are the same values as would be passed to a
readmail_mod, if one were to be used instead.

src\sbbs3\js_global.c(3703): warning C4018: '<': signed/unsigned mismatch
src\sbbs3\js_global.c(3761): warning C4018: '<': signed/unsigned mismatch
src\sbbs3\js_global.c(3779): warning C4018: '<': signed/unsigned mismatch

MsgBase.get_msg_header or get_all_msg_headers), the message header object's
private data (used internally in these C source functions) would be freed and
NULL'd, apparenty as a form of optimization. This would cause some methods
which can accept a msg header object as an argument (e.g.
MsgBase.put_msg_header, bbs.show_msg/show_msg_header) to fail or behave
in strange ways.

Instead of freeing/NULLing the private data (and depending on that as an
indication that the header has been enuemrated), just set a member variable
indicating that the header has been enumerated (once) already.

This is the bug that has been tripping me up with my message lister JS mod
(see YouTube video). I can finally get that committed to CVS for testing now.
:-)

base "status" matches the associated sub-board configuration values (e.g.
from SCFG). Specifically for the properties: max_crcs, max_msgs, and max_age

here, and it's not really needed.

The block sizes for TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 and
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 were incorrect in the suite
definitions.

This is the root cause befind the old cl-suites.patch which disabled
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (no great loss).  This patch also
fixes the TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 suite, which may be what
new Apple phones were negotiating for pop3s connections.

and reported by wkitty42... you can turn ssh back on now. :D

despite them being manditory in the SSHv2 spec.

Version 1.04: Internal change only (no change in behavior for the user) - Updated the way AddAdditionalQuitKeys() is called in the DDLightbarMenu objects, due to the change in dd_lightbar_menu.js

AddAdditionalSelectItemKeys() now takes a string specifying additional keys rather than an array of strings.  For instance, if you want both lowercase 'e' and uppercase 'E' to allow selecting an item, the call would look like this (assuming lbMenu is the menu object):
lbMenu.AddAdditionalSelectItemKeys("eE");

Also, changed AddAdditionalQuitKeys() to work the same way.

Note: If you are using SlyVote, you will need to also update SlyVote, since SlyVote has also been updated to call AddAdditionalQuitKeys() this way.

New function: AddAdditionalSelectItemKeys(), which adds additional keys that can be used to select any item (in addition to Enter).  This function takes an array, and the keys are case-sensitive.  For example, to add the key E to select any item (assuming the menu object is lbMenu):
lbMenu.AddAdditionalSelectItemKeys(["E"]);
To make a case-insensitive verison, both the uppercase and lowercase letter would need to be added, as in the following example for E:
lbMenu.AddAdditionalSelectItemKeys(["E", "e"]);

Also, after showing the menu & getting a value from the user (using the GetVal() function), the lastUserInput property will have the user's last keypress.

base.put_msg_header(). I just happened to notice this while making the last
fix committed. I'm guessing this particular code path hasn't been tested (?)

disabled since the header may later be written back to disk. Should fix
error reported by Ragnarok (DOCKSUD):
imapservice.js line 1763: Error: Message header has 'expanded fields'