filepro menus and Ctrl-S - maybe Anzio setting?

[Kenneth Brody]

On 12/6/2010 5:30 PM, Bill Campbell wrote:
> On Mon, Dec 06, 2010, Kenneth Brody wrote:
>> On 12/6/2010 3:38 PM, Bruce Easton wrote:
>>> A client has a few menus that have nineteen options on them.
>>> The first character on each of these menus is a Ctrl-S.  (I think
>>> dmakemenu starts at Ctrl-A and then goes up by one - up through the
>>> last non-blank option - so on these menus, the nineteenth option
>>> is the last option, ergo the Ctrl-S as the first char in the file.)
>> [...]
>>
>> I don't understand what you mean by "the first character on each of these
>> menus is a Ctrl-S".  How do you get a filePro menu option to be a
>> non-printing character?  (And dmakemenu doesn't "start" at anything, except
>> for 24 menu entries into which you decide what to place.)
>
> Furthermore, ctrl-s can cause problems if dealing with terminals
> that use software flow control where ctrl-s is XOFF, saying stop
> sending data until you send an XON ctrl-q.

I think Fairlight already pointed out that problem.  I was wondering how 
Ctrl-S (or any control character, for that matter) got involved in the first 
place.

And, Ctrl-Q gets eaten by the O/S (assuming the standard xon/xoff settings), 
even if not paused.

And filePro will normally see Ctrl-I as RTAB, not as Ctrl-I.

And...

> When Radio Shack brought out the Model 12/16 it had a number of
> extra keys around the numeric keypad which were set to make life
> easier with Scripsit which used mnemonic ctrl sequences (e.g.
> ctrl-i was insert, ctrl-d delete, etc.).  Almost immediately
> after this came out with Xenix systems, people started calling to
> say that their system had locked up.  They had pressed the
> function key that sent ctrl-s.  Pressing ctrl-q fixed their
> problems.
>
> WordStar used both ctrl-s and ctrl-q as cursor control keys,
> which of course caused problems with serial terminals.

Some years ago, a client had a printer which used Ctrl-S for the "underline 
on" print code.  The printer was attached to a Unix box via serial port. I'm 
sure you can guess the result.

> IMHO, the most egregious demonstration of ignorance of standards
> is Microsoft's use of the single ESC to cancel things as the ESC
> character is supposed to start a command sequence, and is not
> complete without some modifier(s).  This is why FilePro uses the
> ESC-ESC sequence to execute.

-- 
Kenneth Brody