The CTX constructor arguments weren't documented

Some blind beautification via HTML tags

Also clarify (or try to clarify) that the maxlen argument is required if you
want to specify any kmode flags.

Mainly capitalization, but some typos and added details. 

Limited to 6 chars, yet some values are as long as 12 chars.

Also, eliminates this warning from RELEASE builds (only) using gcc version
12.2.0 (Debian 12.2.0-14):
js_uifc.c: In function ‘js_uifc_init’:
sbbs.h:230:56: warning: writing 8 bytes into a region of size 7 [-Wstringop-overflow=]
  230 |                                         (ret)[JSSTSpos]=(char)JSSTSstrval[JSSTSpos]; \
      |                                         ~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~
sbbs.h:242:9: note: in expansion of macro ‘JSSTRING_TO_ASTRING’
  242 |         JSSTRING_TO_ASTRING((cx), JSVTSstr, (ret), (maxsize), (lenptr)); \
      |         ^~~~~~~~~~~~~~~~~~~
js_uifc.c:609:17: note: in expansion of macro ‘JSVALUE_TO_ASTRING’
  609 |                 JSVALUE_TO_ASTRING(cx, argv[1], mode, 7, NULL);
      |                 ^~~~~~~~~~~~~~~~~~
In file included from sbbs.h:255:
/home/rswindell/sbbs/src/sbbs3/../xpdev/genwrap.h:77:20: note: destination object of size 7 allocated by ‘__builtin_alloca’
   77 | #define alloca(sz) __builtin_alloca(sz)
      |                    ^~~~~~~~~~~~~~~~~~~~
sbbs.h:228:43: note: in expansion of macro ‘alloca’
  228 |                         if(((ret)=(char *)alloca((*JSSTSlenptr)+1))) { \
      |                                           ^~~~~~
sbbs.h:242:9: note: in expansion of macro ‘JSSTRING_TO_ASTRING’
  242 |         JSSTRING_TO_ASTRING((cx), JSVTSstr, (ret), (maxsize), (lenptr)); \
      |         ^~~~~~~~~~~~~~~~~~~
js_uifc.c:609:17: note: in expansion of macro ‘JSVALUE_TO_ASTRING’
  609 |                 JSVALUE_TO_ASTRING(cx, argv[1], mode, 7, NULL);
      |                 ^~~~~~~~~~~~~~~~~~

PROP_CHANGES already handled in if() condition
CID 33176

ARE YOU HAPPY NOW CYAN?!?!

Rather than defaulting to zero lines high and the width of the title,
default to the entire screen area.

Reverted the SAFECOPY() NULL source-pointer magic "(null)" string thing as that caused a different Coverity issue. Explicitly check for NULL at the call-sites instead.

Reverted the SAFECOPY() NULL source-pointer magic "(null)" string thing as that caused a different Coverity issue. Explicitly check for NULL at the call-sites instead.

Hopefully not introducing any bugs in the process.

Hopefully not introducing any bugs in the process.

Stop lying. Programming is hard enough already.

Now the default bar is INT_MAX, so it always gets corrected when
left as default.

This is good.

So here's what we're doing now... we set bar so that the first item
shown in the menu is the lowest index possible that still shows cur.
bar is therefore calculated as the displayed item count minus the
distance from cur to the end of the list.

Yeah, that's the easiest way to explain it.

scrn, showbuf, timedisplay, bottomline, getstrxy

bool (JSVAL_FALSE), not number (JS_FALSE).

valid lvalue. In all the use-cases, the variable is a stack variable going out
of scope anyway, so don't bother with nullification.

HANDLE_PENDING() contains a return, so it's theoretically possible that the
memory allocated by the previous JSVALUE/STRING_TO_... allocation could
be leaked. So now we pass an optional pointer to HANDLE_PENDING() which will
call free() on it if it's not NULL, and then sets it to NULL for good measure.

If the old syntax was used (with a list of integers), it would cause a segfault after
displaying a corrupted/small dialog due to lots of problems parsing the argument list.

Currently, the (previously undocumented) top, left, width, dflt, and bar
parameters to uifc.list() are moved into this object and can no longer be
passed in the function call.

This is still only half-baked, so it will need a few weeks at least in CVS
before it congeals enough to be stable.