Datagrid Virtualization 3 pass render question

Radzen.Blazor Components
1

I noticed that for Radzen DataGrid Virtualization, the data load example does 3 passes before rendering content.

What are the reasons top and bottom pages are loaded, but not rendered, and the final pass renders the content?

We tried using Microsoft's Virtualize on it's own with some success, but we noticed issues when clamping text to 2 lines caused flickering as if microsoft virtualize was confused due to clamping. Is Radzen doing these extra load passes to help with the size of the rows? I did a demo with thousands of two line clamped items using Radzen's data load approach, and it worked well, which is good.

Before we spend effort replacing our custom Virtualized grid, I wanted to understand the benefits of Radzen's approach of doing the multiple passes.

image
image1301×792 62.7 KB

thanks
Rob
Radzen Blazor Studio Professional owner

2

Hi @TheRHogue,

I don't think we are doing anything special - it is just how the Virtualize component behaves internally. We are only setting its ItemsProvider property and firing the LoadData event. You can check the source yourself.

3

Thanks. One quick follow up. Have you had any bugs reported on Radzen Grid Virtualization where long multi-line clamping caused flickering during scrolling? I didn't see anything in the forums.

I am going to try and get a spike going to repro our issue using Radzen Grid Virtualization, and see if we can repro in the app environment. My demo under stress worked fine.

thanks
Rob
Radzen Blazor Studio Professional owner

4

Not as far as I remember.