filepro menus and Ctrl-S - maybe Anzio setting?

[Bruce Easton]

(I'm assuming the top post below was later than what was on the bottom; 
I don't think that reply from Bob every made it to me.  Anyway - it 
looks like the exact behavior is answered in the top post below.)

Have you tried making a new menu on the Linux box with 19 options on it 
and calling it from another menu?  Also, could there be something on the 
calling menu option that is changing the environment in some way before 
referencing the target menu?

Bruce

On 12/9/10 12:03 AM, flowersoft at compuserve.com wrote:
> A couple of things have not been mentioned which might throw some light on
> this problem.
> First, the menu options work perfectly in SCO Unix.  Maybe something
> happened when the programs were transferred to the Linux box, but everything
> else seems to be working perfectly.
> Second, the menu behaves normally if called from the command line or
> dpromenu.  In other words, if you type p menuname from the command line, no
> problems.  If you run it from the G option of the filePro menu, no problems.
> It is only when the menus with 19 lines are called from another filePro user
> menu, that the problem occurs and the problem is that Anzio locks the
> keyboard.  You can see it on the last line of the screen.  Anzio displays
> LOCK on it.  Hitting Alt U, unlocks the keyboard and the menu works
> normally.
> So it is something that Anzio is doing but what is triggering it is the
> million Dollar question.
>
> -----Original Message-----
> From: filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com
> [mailto:filepro-list-bounces+flowersoft=compuserve.com at lists.celestial.com]
> On Behalf Of Bob Rasmussen
> Sent: Monday, December 06, 2010 6:30 PM
> To: Bruce Easton
> Cc: filepro-list at lists.celestial.com
> Subject: Re: filepro menus and Ctrl-S - maybe Anzio setting?
>
> On Mon, 6 Dec 2010, Bruce Easton wrote:
>
>> 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.
>> 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.
>> 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?
>> I see you're now talking about vim which I will try.
> If I understand your clarification, it is NOT that the user is typing
> ctrl-S, it's that a menu file that happens to SHOW a ctrl-S (if you open
> it in an editor, which is not recommended) somehow causes a problem.
> Right?
>
> If that is true, and IF filePro somehow displayed (output) that ctrl-S,
> then it is possible that this causes a problem with Anzio (and not with
> PuTTY).
>
> Regards,
> ....Bob Rasmussen,   President,   Rasmussen Software, Inc.
>
> personal e-mail: ras at anzio.com
>   company e-mail: rsi at anzio.com
>            voice: (US) 503-624-0360 (9:00-6:00 Pacific Time)
>              fax: (US) 503-624-0760
>              web: http://www.anzio.com
>   street address: Rasmussen Software, Inc.
>                   10240 SW Nimbus, Suite L9
>                   Portland, OR  97223  USA
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>