summaryrefslogtreecommitdiffstats
path: root/wscript_build.py
diff options
context:
space:
mode:
authorDudemanguy <random342@airmail.cc>2020-08-20 10:24:52 -0500
committerDudemanguy <random342@airmail.cc>2020-08-20 16:57:37 +0000
commit30dcfbc9cb3f77dbb729fb6f95ffde7dbdddc4cb (patch)
treedbf0e27190bca5231f386714a4813a7ab7e9542a /wscript_build.py
parentc9474dc9ed6172a5f17f66f4b7d367da6b077909 (diff)
downloadmpv-30dcfbc9cb3f77dbb729fb6f95ffde7dbdddc4cb.tar.bz2
mpv-30dcfbc9cb3f77dbb729fb6f95ffde7dbdddc4cb.tar.xz
wayland: conditionally commit surface on resize
It was possible for sway to get incorrectly sized borders if you resized the mpv window in a creative manner (e.g. open a video in a non-floating mode, set window scale to 2, then float it and witness wrong border sizes). This is possibly a sway bug (Plasma doesn't have these border issues at least), but there's a reasonable workaround for this. The reason for the incorrect border size is because it is possible for mpv to ignore the width/height from the toplevel listener and set its own size. This new size can differ from what sway/wlroots believes the size is which is what causes the sever side decorations to be drawn on incorrect dimensions. A simple trick is to just explicitly commit the surface after a resize is performed. This is only done if mpv is not fullscreened or maximized since we always obey the compositor widths/heights in those cases. Sending the commit signals the compositor of the new change in the surface and thus sway/wlroots updates its internal coordinates appropriately and borders are no longer broken.
Diffstat (limited to 'wscript_build.py')
0 files changed, 0 insertions, 0 deletions