Page 1 of 1

(RPG) Auto progress to next field

Posted: Thu May 29, 2014 12:19 am
by DavidS
On normal iSeries screens its possible to have fields set so that once the user has entered the last possible character in a field it automatically moves to the next one (example 7 digit customer code will move on after the 7th digit is entered.)
I've looked through the documentation and can't find the correct way to duplicate this behaviour, I was wondering if someone could point me in the right direction please?

Re: (RPG) Auto progress to next field

Posted: Thu May 29, 2014 8:15 am
by MarkDuignan
When the keyboard is displayed on an entry field the user should be able to type the number and then press the 'Next' button to advance to the next field.
The form view displayed behind the keyboard should scroll up to show them what they are now entering.

Re: (RPG) Auto progress to next field

Posted: Thu May 29, 2014 8:20 am
by MarkDuignan
If you run the latest RPG shipped demo -> Human Resources -> Employees.
Touch and employee to see their details.
Touch the 'First Name' field and the keyboard will appear.
Use the Next button to advance to the next field.
Note that when 'Sex" drop down appears the Next and Done buttons are at the bottom.

Re: (RPG) Auto progress to next field

Posted: Thu May 29, 2014 6:31 pm
by DavidS
Thanks for the reply Mark,
The behaviour my customer has asked for is that rather than having to press "next" on the keyboard, the program automatically moves itself to the next input field (so to use the Employees example, if I hit the end of the first name field the cursor would automatically move to the surname field.)

I think on standard DDS the keyword is CHECK(ER), I've tried setting it on two short numeric fields but it doesn't appear to work which is why I was wondering if there's a longrange property that I can assign that would enable the same behaviour.

Re: (RPG) Auto progress to next field

Posted: Fri May 30, 2014 7:29 am
by MarkDuignan
There is currently no feature like that.
5250 DDS are a completely optional and very basic input/output and form layout mechanism for LongRange.
Very few DDS keywords are supported.