-
Notifications
You must be signed in to change notification settings - Fork 697
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: Why is WinUI 3's scroll experience is far from WinUI 2 #5850
Comments
same issues here while on Windows 10 21H1 and Windows 11 |
Dupe #2513 |
Thank you for the reply, I've just confirmed that the scroll experience in Windows App SDK 1.0 is good only if you are using the mouse wheel, it seems that the framerate is still locked to 30fps when you are dragging the slider of the scroll bar instead of using the mouse wheel, and that is not gonna happen in WinUI 2 |
You can find the videos here and the difference is so obvious |
I'm aware of that, thanks for the reply |
@Austin-Lamb @bartekk8 and @RBrid FYI |
I'm just curious if this is still an issue. I'm testing the latest WinUI 3 and 2 Gallery and they seem very similar to me. But perhaps I'm wrong. @dylech30th, @sylveon any updated feedback? |
I just tried both side by side and while it doesn't appear that the WinUI 3 gallery is capped to 60fps anymore, the WinUI 2 gallery still feels smoother to scroll through. |
I can confirm that scrolling in the "All Controls" section of the winui gallery is extremly sluggish compared to the winui 2 version. |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
Open both WinUI 3 Control Gallery and WinUI 2 Control Gallery's Settings page, it seems that the WinUI3 version only got 30fps while the WinUI 2 version has an excellent scroll experience with an adaptive framerate that correlated to the screen's refresh rate, this also happens in my own app built with WinUI 3. If you are using an high-refresh-rate screen, the difference would be even more obvious
The text was updated successfully, but these errors were encountered: