While I am not suggesting this is a good option what the F24=More keys
COULD do is provide a new set of function keys.
For example in the program use a new value "functionKeySetActive"
When F24 is pressed increment / wrap the value for functionKeySetActive
Then everywhere in the program you would need to include;
select;
when functionKeySetActive = 1;
if F01 ... do something
...
if F23 ... do something
when functionKeySetActive = 2;
if F01 ... do something
...
if F23 ... do something
etcetera
Alternatively and in my opinion a slightly better option is to review the
screen design. We have thousands of green screen programs and none are
close to using 24 function keys. If you need that many function keys it
would suggest the too much information is being provided in a single
screen and it should be simplified.
Just my 2 cents worth
Cheers
Don
From: "Booth Martin" <booth@xxxxxxxxxxxx>
To: "RPG programming on IBM i" <rpg400-l@xxxxxxxxxxxxxxxxxx>
Date: 12/05/2020 06:05 AM
Subject: Re: How would one create additional function keys in the
display file.
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx>
Problem is, it still adds up to a limit of 24 keys, each with a single
purpose.
Gardeners call this problem "pot-bound" and they realize their only real
answer is splitting the plant and having more pots. Or a bigger pot,
which for us is not a choice.
On 5/11/2020 2:06 PM, Francois Lavoie wrote:
About doing a multiple record overlay to display alternative fkeys like
(good old) RLU ?
F3=Exit F11=Define field F16=Delete field
F22=Alternative keys F24=More keys
Here, F22 (SF10) shows a different list of fkeys. Repressing F22 shows
the base keys
F19=Left F20=Right F21=System command
F22=Base keys F24=More keys
midrange.com
