Just a quick question guys. If I turn off paging and just virtualize the datagrid, why does it still cap the rows? If I leave the default, I get capped at 10 rows, and it seems the only way to get around that is to put a large number in there...I have a very large table that my client preferrs to scroll through, so I i have to set it to a crazy number.
I tried it on a brand new application with the same results...maybe I am doing something wrong...
Otherwise all items from the table would be selected at once and loaded in memory. This can lead to all kinds of problems.
Ok, I understand that means that with paging off and virtualization on, there are still a finite number of rows that I can display, unless I set it to 999999999. I'll just have to make them understand that I can set the page to a larger number, but they will still have to page to get all rows.
Thanks for the quick reply!
You don't have to do that at all. The PageSize attribute doesn't affect the total number of items displayed. The Blazor Virtualize component itself requests the number of items required. PageSize is only used if it requests 0 items. You can see that for yourself in our demo - no matter what PageSize is Top is always 18.
