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
If a non-maximized, normal window is resized such that its borders are outside the limits of the monitor, the window seems to be seen as full screen by the Rude Window Manager. The taskbar will lose always on top when such windows are in the foreground. This is a failure mode that RudeWindowFixer does not currently mitigate.
This is reproducible using something as simple as Notepad. It's hard to trigger it accidentally though, because resizing a window to exceed the boundaries of the monitor requires some fiddling.
On the other hand, it's relatively easy to accidentally trigger this on the main window of Steam. It's not clear what's different about that window - it might be related to its custom border style, or maybe to its custom "snapping" behaviour when approaching the edges of a monitor.
It also looks like changing monitor resolution and/or scaling can end up resizing windows in such a way as to end up in this situation.
From a RudeWindowFixer perspective, the main challenge in solving this problem is that it's not entirely clear how to reliably distinguish between a window that is intended to be full screen (i.e. where the application deliberately set up the client area to cover an entire monitor), and a window that is accidentally full screen (i.e. this case). If we get this wrong, the taskbar will end up being shown on top of actual full screen applications.
The text was updated successfully, but these errors were encountered:
If a non-maximized, normal window is resized such that its borders are outside the limits of the monitor, the window seems to be seen as full screen by the Rude Window Manager. The taskbar will lose always on top when such windows are in the foreground. This is a failure mode that RudeWindowFixer does not currently mitigate.
This is reproducible using something as simple as Notepad. It's hard to trigger it accidentally though, because resizing a window to exceed the boundaries of the monitor requires some fiddling.
On the other hand, it's relatively easy to accidentally trigger this on the main window of Steam. It's not clear what's different about that window - it might be related to its custom border style, or maybe to its custom "snapping" behaviour when approaching the edges of a monitor.
It also looks like changing monitor resolution and/or scaling can end up resizing windows in such a way as to end up in this situation.
From a RudeWindowFixer perspective, the main challenge in solving this problem is that it's not entirely clear how to reliably distinguish between a window that is intended to be full screen (i.e. where the application deliberately set up the client area to cover an entire monitor), and a window that is accidentally full screen (i.e. this case). If we get this wrong, the taskbar will end up being shown on top of actual full screen applications.
The text was updated successfully, but these errors were encountered: