filepro menus and Ctrl-S - maybe Anzio setting?

[Bruce Easton]

On 12/6/10 6:39 PM, Kenneth Brody wrote:
> On 12/6/2010 6:19 PM, Bruce Easton wrote:
> [... megasnip ...]
>>>
>> OK - let me try to simplify:
>>
>> The behavior on the client menu is that it freezes as soon as the menu
>> is run from option G - and only for the menus that have 19 options on 
>> them.
>
> Not sure why that would happen, since filePro never displays that 
> first byte.
>
>> In my investigation of this (not even on the client's site by the way,
>> but on one of our Linux boxes), I went into vi and notice this
>> correlation about this control char visible at the top and the number of
>> options.  Nothing is freezing up during my investigation.
>>
>> At this point, I'm sure there must be some problem with the termcap, OS
>> terminal configuration, something other than filepro or Anzio - it has
>> to be.
>>
>> In my inital post I say:
>>
>> "The first character on each of these menus is a Ctrl-S."
>>
>> Not exactly sure how to be any clearer about that part - well it's 
>> only once at the top of the file.
>
> And, had that been the only thing you said, it would have been clearer 
> that you meant the first byte in the menu file that you were referring 
> to.
>
> However, you also said:
>
>>> I think
>>> dmakemenu starts at Ctrl-A and then goes up by one - up through the
>>> last non-blank option -
>
> which makes me think that you were saying that the first menu item had 
> a Ctrl-A, the second a Ctrl-B, and so on, up to the 19th with a Ctrl-S.

I see how that  might be mis-interpreted.  I should have stated that a 
bit differently.  I was imagining how dmakemenu might calculate what it 
needed to do to arrive at the control character that would be used.

>
> You also said:
>
>>> Anyway, when they run via Anzio, the screen is frozen when you
>>> arrive at the menu and a Ctrl-Q needs to be typed to unfreeze
>>> the screen.
>
> which makes me think that you are referring to running the menu, and 
> the first byte in the menu file is never shown, so a Ctrl-S as the 
> first byte would have no effect on running the menu.
>
Well - I didn't see it myself, but Cesar said the menu looked normal 
other than you couldn't navigate on it at all or select anything.


>> Since I'm seeing these control characters for the first time in vi,
>> it would be helpful to know - does filepro put the control character 
>> there or not?
>
> If a menu has 19 entries in it, then the first byte of the file will, 
> indeed, be a Ctrl-S.  However, since filePro never shows that to the 
> user (any more than it would show the binary information in the header 
> of a record in the key file), it would have no effect on filePro using 
> it.
>
>> I see you're now talking about vim which I will try.
>
> I'm not sure why you're using a text editor (even if it can "handle" 
> binary files) on the menu.  Why not just use dmakemenu?
>
I only went to look at it that way after he mentioned that only the 
menus with nineteen options had a problem.

We will look at the OS and termcap config to see where the problem is.

Bruce