Pass-through only really does anything useful if the BBS user's client is a
Telnet client and it responds as the server expects. Since the user's
Telnet client (when using one) has already negotiated Telnet options, they
won't ACK options that the server expects them to, so this doesn't really
work. The proxy fixes that issue.

Meaning, it'll negotiate all Telnet options with the remote server (assuming
not an RLogin server), so long as the TG_PASSTHRU option is *not* set.

This allows more Telnet servers to work as expected, especially when the
client (BBS user) is not using a Telnet client!

Fix issue #432

Also arrange section writing order to match scfglib2.c

Avoid build warning about use of deprecated /Gm option.

... for uifc/ciolib settings

And make default video mode LCD 80x25

This should fix the Win32 build.

This problem doesn't happen with the .bin version of these scripts.

Thanks for the reminder, Keyop

If this key doesn't exist, the default value is used

So it's not a big deal if your ctrl/attr.ini file is missing or doesn't have
any particular key in it.

For Nelgin

For controlling the UIFC/CIOLIB properties (scaling, modes, etc.)

Copied from read_scfg_ini() in scfg.c

Fix issue #760

UINT_TO_JSVAL automatically handles the storage as the necsesary underlying
type in the JS engine.

Values > 0x7fffffff (2147483647) will still be stored (and re-written) as
doubles and could be problematic.

Fix issue #759

New key "rainbow" in ctrl/attr.ini
New Ctrl-A codes: 'X' to turn on repeating/wrapping rainbow attributes,
 'x' to turn on non-repeating/wrapping rainbow attributes.
New @-code: RAINBOW:x to set the list of (comma-separated) rainbow attribute
 values (in same form as attr.ini).
 When used in a display file, the rainbow attribute change is temporary.

Ever wanted to add alternating attributes to @-code expanded text in display
files? Now you can.

Also can be used to easily/quickly create display files with repeating
elements (e.g. commands/options) using alternating attributes.

Previously, we only cleared hotspots when executing any external from the
external program section (doors menu). This means that invoking a script or
external program (e.g. via JS bbs.exec()) from anywhere else, any current
mouse hotspots would remain active. Disable those.

This fixes issue #758

The extra characters (comments) are ignored when parsing this particular file,
so though this is not how we normally add comments to .ini files, it still
works fine in this case.

Another legacy config file replaced with .ini file (for easier editing and
future extensibility).

No longer dynamically allocate scfg_t.colors (no need). There's really no
reason why this is still an array, but leave as is for now.

Also, I noticed JS console.color_list (also an array) is not enumerable
(or documented) - that should be fixed.

This was a loop-hole that caused Denn (OUTWEST) some confusion, those his
QWKnet account could post polls, it could not post messages due to having the
P-restriction.

Fixes error reported by Rowyn Sand (Ravne) with accepting a marriage
proposal (issue #757)

client_t.protocol is no longer a pointer.

Warnings reported by gcc (Debian 12.2.0-14) 12.2.0

... rather than calling textmode() after.

This solves the problem of black bars above and below the UIFC window in
echocfg and SCFG on ChromeOS, at least.

All keys are now in the root/global section and they are now:

video_mode (default: 42)
uifc_mode (default: 0)
ciolib_mode (default: 0)
scaling (default: 0)
lines (default: 25)
insert (default: false)
esc_delay (default: 25)

These global variables weren't actually used for any purpose.

If a sysop wants to override the default user interface/console I/O library
behavior of SCFG without using command-line arguments, they can create a
ctrl/scfg.ini file with the following optional [section] keys:

[uifc]
mode (advanced uses, e.g. disabling mouse support)
height (in lines)
insert (keyboard insert mode, not overwrite)
esc_delay (ESC-key delay)

[ciolib]
mode (advanced uses)
scaling (fractional values, e.g. 1.5, supported)
height (in pixels)
width (in pixels)

Command-line arguments take precedence over scfg.ini settings (if set).

The scfg.ini file is read *before* parsing command-line args, so if a ctrl
directory is specified on the command-line (e.g. rather than via environment
variable), the scfg.ini file won't be read from that specified location but
rather the default (/sbbs/ctrl) or the SBBSCTRL env var value.

Another attempt to make Nelgin happy and close out issue #749, though no, this
doesn't auto-save the current parameters (you'll have to create/edit the
scfg.ini file by hand).

Fix issue #754

SlyEdit: In SlyEdit_Misc.js, check to see that xtrn_area.editor[user.editor] is an object before using it.  Should help with #755.

See merge request !436

SlyEdit: In SlyEdit_Misc.js, check to see that xtrn_area.editor[user.editor] is an object before using it.  Should help with #755.

I'm not clear why Walnut Creek would list files (e.g. readme.txt) in these
lists of "directories", but don't create file areas for them. Less clean-up
required after import.