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
{{ message }}
This repository has been archived by the owner on Feb 9, 2024. It is now read-only.
When I make the application fullscreen, the border edge seems to overlay the other monitor.
The above image shows how the window border is for some reason thicker when fullscreen, versus the below image that is the normal window.
I am unsure if there's a logical answer for the border width increasing and overlapping the other screen, just thought I'd make an issue if this is something fixable.
The text was updated successfully, but these errors were encountered:
I'm sorry, but I don't understand what the problem is. Can you explain it more clearly?
@seo-rii When you maximize a window, the border on the left and right side of the application become increased by 5px, overlapping content on the other screens.
First screenshot I sent shows the border (that shouldn't be there) while the application is maximized.
Second screenshot shows how there is no border when the application isn't maximized.
Sadly, it seems difficult to solve this bug. I don't even know why this bug is happening. The code that applies custom aero effect did not cause any problems, and even if you turn them off, the same problem occurs. Other similar programs (a non-UWP implementation of the acrylic window) were found to have bugs, but not to mention the solutions to these bugs. If you know the solution, please send me a PR or let me know here. I'm so sorry.
When I make the application fullscreen, the border edge seems to overlay the other monitor.
The above image shows how the window border is for some reason thicker when fullscreen, versus the below image that is the normal window.
I am unsure if there's a logical answer for the border width increasing and overlapping the other screen, just thought I'd make an issue if this is something fixable.
The text was updated successfully, but these errors were encountered: