4gl back arrow code
A 4GL developer found users could no longer use the back/left arrow to move to previous fields in an INPUT screen, and asked what key to trap. Replies said no explicit coding is needed: arrow navigation is built in (ON KEY (LEFT); CTRL-H/backspace is reserved), and the cause is more likely application logic or form attributes - AFTER FIELD validation or NEXT FIELD forcing the cursor, REQUIRED/INCLUDE attributes, or upscol settings; moving cross-field checks to AFTER INPUT was suggested, plus using the 4GL debugger and checking TERM/INFORMIXTERM termcap/terminfo key definitions. The poster never replied, so no confirmed resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
I have a 4gl screen that was working fine in the sense that users were able to back-arrow thru the fields, therby backing up to correct something. I have never included code to handle this problem, it was always implicit. My question is I suppose, what is the KEY catch for a back arrow in a 4gl screen? Or am i looking at the problem wrong? Sorry for lack of code, it consists of "after field" type calls, i am just confused because i never had to explicitly handle back-arrow cases. Joe money out, thanks for any help
monkeys paw wrote: > I have a 4gl screen that was working fine in the > sense that users were able to back-arrow thru > the fields, therby backing up to correct something. > > I have never included code to handle this problem, > it was always implicit. My question is I suppose, > what is the KEY catch for a back arrow in a 4gl > screen? Or am i looking at the problem wrong? > > Sorry for lack of code, it consists of "after field" > type calls, i am just confused because i never had > to explicitly handle back-arrow cases. > > Joe money out, thanks for any help The backspace left arrow is CTRL-H and you can't use that, it's reserved. The left arrow in the up/down/left/right set is LEFT. -- Ian Hotmail is for spammers. Real mail address is igoddard at nildram co uk
monkeys paw wrote: > I have a 4gl screen that was working fine in the > sense that users were able to back-arrow thru > the fields, therby backing up to correct something. > > I have never included code to handle this problem, Problem? what problem? > it was always implicit. Navigating back and forth from field to field doesn't require explicit coding. > My question is I suppose, > what is the KEY catch for a back arrow in a 4gl > screen? on key (left) on key (control-h) > Or am i looking at the problem wrong? I expect so. > > Sorry for lack of code, it consists of "after field" > type calls, i am just confused because i never had > to explicitly handle back-arrow cases. Nor should you. Perhaps your code is using "next field" to force the cursor somewhere the user doesn't want it to go. > Joe money out, I guess that phrase means something in your part of the planet? I wonder what? > thanks for any help My hovercraft is full of eels. -- RGB
RedGrittyBrick wrote: > > My hovercraft is full of eels. My nipples explode with delight! -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com
Obnoxio The Clown wrote: > RedGrittyBrick wrote: >> >> My hovercraft is full of eels. > > My nipples explode with delight! > Which reminds me - if the OP is using an "after field" clause to check the consistency of two fields, the OP might consider moving that check to an "after input" clause to prevent the kinds of navigational problems cryptically alluded to. -- RGB 46 Horton Terrace
Are you just unable to navigate to a previous field ? Are you getting any error message displayed ? Is there a AFTER FIELD on the field you are in, thats stopping you? Is there a REQUIRED or INCLUDE on the field in the form ? Anything in upscol ? You said it 'it was working fine' - so what did you change ? On Monday 05 January 2009 23:54:59 monkeys paw wrote: > I have a 4gl screen that was working fine in the > sense that users were able to back-arrow thru > the fields, therby backing up to correct something. > > I have never included code to handle this problem, > it was always implicit. My question is I suppose, > what is the KEY catch for a back arrow in a 4gl > screen? Or am i looking at the problem wrong? > > Sorry for lack of code, it consists of "after field" > type calls, i am just confused because i never had > to explicitly handle back-arrow cases. > > Joe money out, thanks for any help > _______________________________________________ > Informix-list mailing list > Informix-list@iiug.org > http://www.iiug.org/mailman/listinfo/informix-list -- Mike Aubury http://www.aubit.com/ Aubit Computing Ltd is registered in England and Wales, Number: 3112827 Registered Address : Clayton House,59 Piccadilly,Manchester,M1 2AQ
It's been many years but as a last resort I would use 4GL debugger. I think it was called r4gl. -L.S.
monkeys paw wrote: > I have a 4gl screen that was working fine in the > sense that users were able to back-arrow thru > the fields, therby backing up to correct something. > > I have never included code to handle this problem, > it was always implicit. My question is I suppose, > what is the KEY catch for a back arrow in a 4gl > screen? Or am i looking at the problem wrong? > > Sorry for lack of code, it consists of "after field" > type calls, i am just confused because i never had > to explicitly handle back-arrow cases. > > Joe money out, thanks for any help You don't need to code anything specific in 4GL to handle function keys and arrow keys.4GL uses predefined terminal specifications. Depending on your platform (hw and os) you will either be using termcap or terminfo. Termcap and terminfo contains the key definitions for various terminals. Contains also semi graphic definitions used by curses, so you can get nice frames around your windows. Read the MACHINE SPECIFIC NOTES for your platform. Use INFORMIXTERM to choose terminfo or termcap. Use TERM to choose your terminal definition. If you use termcap, you can either use the standard termcap /etc/termcap or the 4GL provided termcap $INFORMIXDIR/etc/termcap. You can edit termcap difinitions with a standard editor. If you want to change terminfo, you must compile it with the tic command.