Freeze when scrolling (when many records are loaded in the control)

[harinikmsft]

From @gianni-rg on May 2, 2018 17:20

Using the Sample App (but I also tested in another app I'm developing, with same behavior), by incrementing the sample data up to 1M records, the data is loading fine, but as soon as one tries to jump around the dataset using the scrollbar, the control freezes. Going up and down one record at the time (ie. using keyboard up/down arrows) it works fine. I know that loading such a big dataset is not the best way, but I was trying to test control limits (and comparing it with a DataGrid for Xamarin.Forms I'm currently using and which works fine).

Copied from original issue: harinikmsft/datagrid_win10#16

[harinikmsft]

From @dotMorten on May 2, 2018 18:16

I'd like to be able to provide a datasource that tells the datagrid how my rows I got, but I don't need to load any of them. So if I return 1mio rows and the user pulls the scrollbar halfway down, the datagrid will request rows 500000-500020, which I'll then go and fetch asynchronously.
So it's like the incrementally loading interface, but with the ability to skip items. All this so I don't have to download, parse and allocate 500020 rows, just to show 20 rows.

[JohnnyWestlake]

If it can be implemented the same way ListViewBase expects data virtualization (see Random access data virtualization here) that would be most advantageous.

[michael-hawker]

@harinikmsft is this an issue we should prioritize for the 6.0 release at the end of October, especially if we have a repro?

[ghost]

Thanks harinikmsft for patiently waiting while the team is still investigating the issue.

@anawishnoff @RBrid can we please have an update on this issue? Thanks

[ghost]

Thanks harinikmsft for patiently waiting while the team is still investigating the issue.

@anawishnoff @RBrid can we please have an update on this issue? Thanks

[ghost]

Thanks harinikmsft for patiently waiting while the team is still investigating the issue.

@anawishnoff @RBrid can we please have an update on this issue? Thanks

[ghost]

Thanks harinikmsft for patiently waiting while the team is still investigating the issue.

@anawishnoff @RBrid can we please have an update on this issue? Thanks