Most of the grids in the Dealertrack application are loaded one page at a time. However, there are a few exceptions where the grid is loaded with all the data at once.
This issue I am having is that loading all data into the appears to work when control does not come back to the RPG program. Clicking on the previous and next links in the grid works as expected. However, when pressing the page down keyboard button, the grid pages down but then re-displays the first page. It happens so quickly that it appears as though no paging takes place. The properties for the grid are below. What properties need to be set in order for the page up and down keys to behave like the grid previous and next links? Does paging via keyboard keys require RPG coding to handle things properly?
Interesting... I have not heard of this. I just ran a quick test on a subfile program we already had, and the page up/page down keys seemed to work as expected... page down went to the next page, page up went back to the first page.
It was a little weird when I tried it on a screen that had more than one subfile on it. In this case, both subfiles did page down when I hit the page down key, and both did page up when i hit the page up key. Kinda weird -- but seemed to work fine, otherwise.
Not exactly sure what you tell you. I can take the settings you've posted and try to see if I can reproduce the problem, I guess... What would help a lot, though, would be if you post a Ctrl-F9 json dump of the screen. Just go to the screen where you're having the problem, press Ctrl-F9 and it will ask you to download a file named json.txt (or similar.) Upload that file here, and that will let me "replay" your screen on my machine so I can see what's happening.
What is confusing is how to wire the keyboard pageup and pagedown keys to behave the same as clicking either the previous or next links, without returning control to the RPG code.
I have a pretty good idea how to process the next or previous events and control whether the previous or next links are clickable when specifying the page down condition, response and page up condition and response. I do this when implement loading one page at a time. It seems reasonable that the page up and page down keys would be able to invoke the same functionality as clicking the previous or next links.
The JSON dump you sent does not use the "Next" and "Prev" links. Instead it has a scrollbar... so I'm not sure whether this is the one you wanted to send or not?
But, it looks like the problem is that you've told it to send control back to your RPG program when the user hits the end/start of the subfile. This is done with the "page up response" and "page down response" properties. If you leave these unbound, then the pageup/pagedown will just page through the data you've loaded. When you have them bound to indicators, then when it hits the start/end of the data, it will return control to your RPG program with the response variable set, and expect your RPG program to do further processing. (Just as green-screen does.)
Is this the problem you're referring to?
I wrote a display using the settings you posted in your first screenshot in this thread (the screenshot that just showed grid settings) and I set all of the settings identically to what you had. (Which did not include the page up/down responses) and it worked pefectly, clicking the next/prev links or pressing page up/page down worked exactly the same as each other.
Perhaps I'm not understanding the issue, but it seems to work well for me. Could it be a difference in the browser I'm running? Or the version of Profound UI?