mouse button is pressed.

This makes the X10 mode much better, allows copy (but not paste), and
prevents weirdness with button releases when dragging.

While this may or may not be what xterm does, it's clearly the best choice.

input buffer when we stop the mouse.

command from passing the mouse release event in transit (and getting garbage
input to a next command).

We may need a one-shot mouse thing or something like that...

events are enabled.

type).
Fix typo line 454 ReferenceError: paseInt is not defined, reported by Coz!

window.

Only allow clicking the exact cell, not the surrounding ones.

Copyright year 2020.

behavior either globally or per-module.

globally and per-module. Command-line options still take precedence.
For jsdoor builds, jsdoor.ini is supported in whatever directory jsdoor is run
from.
Changed the default log level from Debug to Informational.
(If you need the old default, set LogLevel=debug in your ctrl/jsexec.ini file).

Update Copyright year to 2020.

invalid string in the exception message.
When a file fails to open, include the error value in the exception message.
When there is a socket error, include the error value in the exception message.

Version 1.30: The message list features now uses DDLightbarMenu rather than the internal lightbar menu code.  Requires the latest dd_lightbar_menu.js (in sbbs/exec/load).
Later I also plan to update the area chooser code to also use DDLightbarMenu and remove the internal lightbar chooser code from DDMsgReader altogether.

bak in and ignore it.

Use it in lightbar.js
???
Profit

text to an empty strings ("") in the ctrl/text.dat file, even the Name/Alias
prompt! Now this does mean that only terminal protocols where the username
is provided as part of the negotiation could be used to create new user
accounts (i.e. not Telnet), which I suppose could be fine for an RLogin-only
game server
.
If no user name is supplied by either protocol or prompt, an error is logged
and the function fails.

Fixed bug: for RLogin and SSH, if an invalid (e.g. blank) passsword was
provided during the handshake, an "Invalid Logon" would be displayed followed
by a "Passowrord: " prompt, giving the user an opportunity to reenter the
correct password. Only problem: this only worked for sysop accounts. Normal
users would just be disconnected after they entere (any) password, correct
or not.

This bug is very old in the RLogin support and appears to have been copy/pasted
for the SSH Login bit too.

and RLogin attempts.
It looks like someone copy/pasted the wrong lines from login.cpp.

set them appropriately.

an invalid login for a random (the last read?) user account with a user number
of 0.