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
I'm trying to create a custom window following Microsoft's example here. Everything works fine when using a single screen or multiple screens with the same scaling.
However, when I have one screen set to 250% scaling (4K) and another at 100% scaling, a large white border appears at the top of the window when maximized on the screen with the lower scaling.
I noticed the same issue in the WinUI Gallery App, which behaves similarly on my second screen, just like my own implementation. This suggests that it's not an issue with my code but rather a general problem.
Has anyone encountered this before? Is there a known workaround or fix for this behavior?
Thanks in advance! 😊
Steps to reproduce the bug
Open WinUI Gallery on different screens with different scaling.
Describe the bug
I'm trying to create a custom window following Microsoft's example here. Everything works fine when using a single screen or multiple screens with the same scaling.
However, when I have one screen set to 250% scaling (4K) and another at 100% scaling, a large white border appears at the top of the window when maximized on the screen with the lower scaling.
I noticed the same issue in the WinUI Gallery App, which behaves similarly on my second screen, just like my own implementation. This suggests that it's not an issue with my code but rather a general problem.
Has anyone encountered this before? Is there a known workaround or fix for this behavior?
Thanks in advance! 😊
Steps to reproduce the bug
Open WinUI Gallery on different screens with different scaling.
or
Follow the simple example from Microsoft here
Expected behavior
Full screen without any white border on all screens
Screenshots
NuGet package version
WinUI 3 - Windows App SDK 1.6.5: 1.6.250205002
Windows version
Windows 11 (24H2): Build 26100
Additional context
No response
The text was updated successfully, but these errors were encountered: