Some of you (actually, a great many I presume) have been finding a bug in the
current version of QCTerm's graphic code. If you get a "subscript out of
range" error when you're running one of the several examples that use
clickable buttons, it's because we forgot to initialize a variable.

The clickable buttons were designed to operate primarily with the mouse (and
to my knowledge, everything works well when you use only the mouse). But
we've put in some test behavior into the current version of QCTerm to see if
we like it. Based on our testing, it probably isn't going to stay. But it's
in there at the moment.

What this new behavior does is allow you to select a clickable object by
pressing the arrow keys until you get on the button you wish -- and then
press the RETURN key to select the button, creating an identical event as if
you were mouse-clicking on the screen.

The error occurs if you press the RETURN key BEFORE a button is "selected"
with the arrow keys. In that case, the subscript value identifying the button
simply isn't there. You will encounter this error in any program that has
clickable objects (chess, mapdemo, hal9000e, etc.). I personally like this
feature (your hands never have to leave the keyboard), but in addition to the
error I've outlined here (which is minor), we're having substantial
philosophical problems in keeping the feature in QCTerm due to the behavioral
overloading of the arrow, tab, and CR keys.

These kinds of problems are simply part and parcel of using code that is
still warm from the factory forge, especially when we haven't even decided on
the final form of its behavior.

Nonetheless, my apologies.

Wirt Atmar