Wayland Backend Window Sizing and Behaviour Incorrect on Scaled Displays as of `7f3f82b`
sonic2kk opened this issue · comments
As of 7f3f82b the window sizing and behaviour is incorrect with the Wayland backend when the window is opened on a scaled display. While this commit fixed the mouse offset (which I am very glad about) it has also introduced other regressions on scaled displays.
The window will open with a size and internal resolution of 1280x720 when opened on a non-scaled display. But when opened on a scaled display, the sizing is wrong.
If opened on a non-scaled display and then moved to a scaled display, this happens to the window.
Note the increased size and the incorrect titlebar placement. This titlebar behaviour can be fixed when clicking on the blank area at the top where the titlebar should appear.
When focusing (either by clicking or tabbing into) a window on a scaled display, the size will increase each time.
Maximising a window will cause it to spread over many displays, in my case it spreads over most of my three bottom displays and part of my top display (my primary display is to the left). I notice that when trying to open a window fullscreen, the resolution seems to be entirely wrong. Some lines say pipewire: renegotiating stream params (size: 8634x4857) and others say pipewire: renegotiating stream params (size: 5756x3238). The scaled display is 3840x2160, scaled to 150%, so an effective resolution of 2560x1440.
If the window is focused in and out a few times, and then moved some amount beyond the leftmost display, the size of the window increases even more. I took a screenshot using KDE's Spectacle utility, which as I have configured it includes the window titlebar and shadow, but to illustrate how big the window can go, the screenshot resolution was 14,609x8,292.
If a GameScope window is opened on, interacted with, or otherwise used on a non-scaled display, it functions absolutely fine.
Fixd
Just tested and it works, thanks so much 😄