|
How about: D Function_Keys DS D KA D KB D KC ... D KY D F1_Pressed N Overlay(Function_Keys:1) D F2_Pressed N Overlay(Function_Keys:2) Could be a lot to type the first time, but you could /copy it where you need it. Joe Giusto II Patuxent Publishing Company <mailto:jgiusto@patuxent.com> mailto:JGiusto@patuxent.com http://www.lifegoeson.com <http://lifegoeson.com> -----Original Message----- From: Hatzenbeler, Tim [SMTP:thatzenbeler@clinitech.net] Sent: Monday, August 16, 1999 7:02 PM To: 'RPG400-L@midrange.com' Subject: Named Indicators... I have in the past used named indicators in this way. 0020.00 d InPtr s * inz(%addr(*in)) 0021.00 d Indicators ds Based(InPtr) 0023.00 d ReqCtl_SflDsp... 0024.00 d n Overlay(Indicators:81) 0025.00 d ReqCtl_SflClr... 0026.00 d n Overlay(Indicators:82) 0027.00 d ReqCtl_SflEnd... 0028.00 d n Overlay(Indicators:83) But I could not get the %addr to work with indicator based function keys(INKA-KY). I tried %addr(*ink) but that didn't do the trick, and I did notice that around position 101 or so, the *ink were triggering values there, but I didn't want to write code that was I couldn't find documentation in softcopy for... I know I can map a normal *indicator such as *in03 to functionkey3 and define the DDS to make the function key3 to trigger *in03, but I wanted to use the reserved values of *inka-y. Thanks, tim +--- | 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-2024 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.