× 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.



Myself, I only use indicators when I absolutely have to in RPG IV, that
being display files.  Being such, I have all 99 indicators to use.

I simply use *IN01 through *IN24 for function keys, and pick some indicator
in the 80's range with a comment at the top to explain it's usage.  Subfiles
use the most.

One of the biggest reasons I like this is if I'm looking for an indicator
usage in a program, such as 89 which I saw in the sub file, I'll open up the
source and search for 89.  And if that indicator is used, I'll find it
quickly.  If the indicator is called SFScrollDown or something, I'm not, and
I'm going to have to go digging through copy sources to find out what
indicator 89 is called.

I still believe in the KISS principle.

Regards,

Jim Langston

-----Original Message-----
From: Carel Teijgeler [mailto:COTeijgeler@chello.nl]

Having read some messages in the thread, I would like to ask those who
favour *INKx for indicators:
how do you define indicators for HELP, ROLLDOWN/PAGEUP, etc., which are
also function keys, but not covered by the *INKx indicators?

I prefer the named constants and AID approach: no indicators, a simple
/COPY member that can be used in all interactive programmes with DSPF's,
only have to be defined once.

Just my Euro-cent.

Regards,
Carel Teijgeler.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.