You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A simple demo app with a page that has 3 DataGrids with 20 rows and 8 columns takes ~1s to display, with 600ms going into layouting. It might be that I am doing something completely wrong, but I couldn't find a way to bring things up to speeds where users wouldn't notice the blocked UI thread.
Are 160 elements too many for DataGrid?
Regression
No response
Reproducible in sample app?
This bug can be reproduced in the sample app.
Steps to reproduce
- `git clone [email protected]:Trolldemorted/WinUI3DataGridTest.git`
- start with profiler
- click on the button to navigate to the test page
Hello Trolldemorted, thank you for opening an issue with us!
I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌
Describe the bug
A simple demo app with a page that has 3 DataGrids with 20 rows and 8 columns takes ~1s to display, with 600ms going into layouting. It might be that I am doing something completely wrong, but I couldn't find a way to bring things up to speeds where users wouldn't notice the blocked UI thread.
Are 160 elements too many for DataGrid?
Regression
No response
Reproducible in sample app?
Steps to reproduce
Expected behavior
New page renders quickly
Screenshots
Windows Build Number
Other Windows Build number
22H2 (Build 19045.3324)
App minimum and target SDK version
Other SDK version
No response
Visual Studio Version
2022
Visual Studio Build Number
17.6.4
Device form factor
Desktop
Nuget packages
CommunityToolkit.WinUI.UI.Controls.DataGrid 7.1.2
Microsoft.WindowsAppSDK1.3.230724000
Microsoft.Windows.SDK.BuildTools 10.0.22621.756
Additional context
No response
Help us help you
No.
The text was updated successfully, but these errors were encountered: