Subfile Load restirctions

[bsinclair]

I have built a sub file with 19 fields and used the new overflow 'Scroll' options to view the records since the screen is over 2500px wide. Since this screen is well out of sight on the right side I am unable to use 'expand to layout' option on the grid and because of this I am limited to 99 records displayed in the sub file. My question is why when we use 'Expand to Layout' the subfile is dynamic and will show all records loaded in the sub file but not using the "expand to layout" we are restricted to 99 displayed records. I have tried using the new getObj("Grid1").grid.setNumberOfRows(count) and though this works in expanding the sub file is doesn't work well with large volumes of records. I was working with over 2500 records in the sub file and yes it did expand and load the data but it was not functioning correctly with all those records and took quite some time to load.

I have tried to expand the layout off the page but then the vertical scroll bar is off out of sight and horizontal one doesn't work right.

Any help would be appreciated.

[Scott Klement]

What version of Profound UI are you running? Starting with version 4.7.1, if you put a grid inside a "simple layout" where the "overflow X" has been set to allow scrolling, the vertical scrollbar for the grid will automatically be locked to the layout border so that it does not scroll off the screen when scrolling left/right.

Using "expand to layout" doesn't make any sense for the situation you are describing. Expand to layout adjusts the length of the subfile so that it fits the size of the layout that it is within. This is mainly useful for mobile applications when you want the number of rows/cols to expand to fill the screen when the subfile orientation changes.

It sounds like for some reason you want to put more than 99 rows on a screen at once. This can be done, as you already know, by calling a JavaScript API. However, we do not recommend this due to the performance issues it causes. Profound UI deliberately only draws the subfile rows as you page them onto the screen, it does not draw them all at once because that would require a lot more work for the browser/PC, and it will slow you down. So while it's possible to bypass the number of rows by calling a JavaScript API to put more than 99 on the display at once, we don't recommend this. It's much better to let PUI handle the scrolling instead of making a vertically scrollable page or layout because it gives PUI the ability to handle the scrolling, which it can do much more efficiently.

You also mention that something is malfunctioning when you set the number of rows larger? That's an issue that I'm not aware of. Slowness, yes, that I know about -- but not a malfunction. Can you explain what's happening?

[bsinclair]

I understand everything you said but I am still not getting the scroll through the whole sub file. I load all 2500 records in the sub file and allow PUI to display it but I only see the 99 displayed records visible. How do I get to see the other 2401 records?

We are currently running PUI 4.8.0. The issue I saw with large volumes of data was the sub file wouldn't scroll at all and the visibility of the data would change. some fields would almost disappear until I moused over them then the data would be visible again. I am sure it is a "too much data' issue.

if it would help I can send all the info to recreate the issue.

Thanks
Bill

[Scott Klement]

The 99 is the limit in the visual designer for the "number of rows" property, which controls how many rows fit on the screen at once (similar to the SFLPAG keyword in green-screen). The limit on the total size of the subfile (which is controlled by the 'subfile size' property, equivalent to the green-screen SFLSIZ keyword) is 9999 rows. Therefore I assumed you were talking about the size per page, since that's where the 99 limit is.

So here's my suggestion:

• Set the 'number of rows' property to a relatively small number, maybe 20 or 30, whatever fits nicely on your screen.
• Set "subfile size" property is large enough to contain all 2500 rows. (You can just make it 9999, there's no harm in this when doing a load-all subfile.)
• make sure the scrollbar is turned on by making sure the 'scroll bar' property is set to 'sliding'
• make sure the subfile is inside a 'simple container layout' widget. To do this, drag the layout onto the screen, temporarily size it large enough for the whole subfile to fit, then drag the subfile into it, you'll see the layout change colors to notify you that the subfile was added to the layout. (If you don't do this, they may just be overlapping on the screen, and it'll look like it's in the layout, but it's really not.)
• make sure the 'overflow x' property of the simple container layout is set to 'scroll'
• when you're done working on it, change the 'width' property of the layout to a smaller size (so that it's no longer too large for the screen). Now when you run your program, it'll let you scroll right/left.

That's all I can think of right now. Let me know if that helps.

[bsinclair]

I had already done everything you suggested and the subifle and scolls work great.. that is not the issue.

I have 2500 records in the subfile and I have 99 displayed by scolling up and down, how do I see the other 2400? The up and down scroll only displays the 99 displayed records.

Thanks

Bill

[Scott Klement]

The only reason that I can think why that would happen is that you made your subfile show 99 rows per page, and have set "overflow Y = scroll" so that you can scroll up/down using the simple layout. This is not, however, the way I would suggest doing it... instead, I would have the number of rows per page be the right amount to fit (without scrolling the layout), and I would have "overflow y" unset. Then I would use the scrollbar in the subfile to do the up/down scrolling rather than the scrollbar on the layout.

If that is not the case, then you're encountering something I've never seen before. In that case, please get the malfunctioning screen to display, then press Ctrl-F9 to make a JSON dump of the screen and send it to me.

[bsinclair]

well you are right.. I had already figured it out by the time I got this message but what you stated is exactly what I found I had done.

Thanks for sticking with me on this.. sorry for the confusion.

Bill