Hi,

i have listgrids where i want them to load dynamically when user scrolls down. To avoid having to count total rows every time, i just check if returned rows is equal to requested rows. If it is, i just set totalrows to (endRow + dataSize). This has worked well.

When trying a new function, i did the above, but instead of adding datasize to the total rows, i just added +1. So the formula was this:

when fetching row 0-75, total rows returned from server was 76 instead of my "normal" value of 150. Next time the total rows would be 151 instead of the normal 225 etc.

I noticed that this had a strange side-effect. Even though only 22-23 rows were visible on-screen in the ListGrid, whenever i load the page, two fetch requests are triggered at once. First 0-75 and then 75-150.

If i change back the "total rows-calculation" to endrow + 75, it goes back to only fetching the first 75.

To me, this is very peculiar. Is this really expected behaviour? Using 6.0-p20171202 at the moment.

i have listgrids where i want them to load dynamically when user scrolls down. To avoid having to count total rows every time, i just check if returned rows is equal to requested rows. If it is, i just set totalrows to (endRow + dataSize). This has worked well.

When trying a new function, i did the above, but instead of adding datasize to the total rows, i just added +1. So the formula was this:

when fetching row 0-75, total rows returned from server was 76 instead of my "normal" value of 150. Next time the total rows would be 151 instead of the normal 225 etc.

I noticed that this had a strange side-effect. Even though only 22-23 rows were visible on-screen in the ListGrid, whenever i load the page, two fetch requests are triggered at once. First 0-75 and then 75-150.

If i change back the "total rows-calculation" to endrow + 75, it goes back to only fetching the first 75.

To me, this is very peculiar. Is this really expected behaviour? Using 6.0-p20171202 at the moment.

## Comment