|
Buck, You can test the *status feedback for zeros and that tells you explicitly that the enter key was pressed. 00002 tells you that a CF key (of any kind, so test the aid byte) was pressed and (no manpage in front of me), but 0133x is a timeout. Darn, I didn't memorize the timeout *status feedback, I guess I can forget that certification =:-o It's a personal style thing. I like the *status feedback in my mainline code: exfmt display status caseq *zeros $enter status caseq 00002 $cfkey status caseq 01121 $print status caseq 01122 $rup status caseq 01123 $rdn status caseq 01124 $help status caseq 01126 $home status caseq 0133x $timer end IMO, using the status gives one a catagory of action before burning cycles to test aid bytes. The sweet part is: no indicators! Buck Calabro wrote: > >Try using the AID byte for your display files, > >I can almost guarantee you will not go back. > > The one advantage that the AID byte has over all other methods is that you > can specifically test for the ENTER key, rather than assume Enter was > pressed because none of the other CF keys' indicators were turned on. > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.