× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



One suggestion I have Jason is that you avoid using the *INKx function key
names. That's just a personal opinion but I hate having to debug a program
and sit there and go

"Hmm...let's see...this program uses *INKO here so what is that? Let's see
that's *IN01=*INKA, *IN02=*INKB, *IN03=*INKC, *IN10=*INKJ...*INKM=*IN13,
*INKN=*INK14...OK. *INKO = *IN15".

All that just so I can figure out which actual function key the user
pressed.

I personally use only numbered indicators when it is necessary to use them
at all, such as in a display file.




-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Jason Cawood
Sent: Monday, October 01, 2007 11:32 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Help with Function Keys in a subfile

I'm working on my first subfile program and I'm having trouble with
the *inkl indicator not setting it to *off.

I've only been working with RPGIV for a little over a year now and
have learned a lot from the posts all of you have left.

Here is the section I'm having trouble with.

C @getord begsr
...
C DoW *inkf = *off
C and *inkc = *off
C and *inkl = *off

C Write Footer
C ExFmt SUBCTL

C EndDo

C If *inkf = *on
C Eval *inkf = *off
C EXSR @ChkChg
C EndIf

C ENDsr
*--------------------------------------------*
C @ChkChg BegSR
...
C If *inkl = *on
C Eval *inkl = *off
C Exsr @getord
C EndIf
...
C ENDsr






As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.