diff options
| author | Dudemanguy <random342@airmail.cc> | 2024-02-24 22:59:27 -0600 |
|---|---|---|
| committer | Dudemanguy <random342@airmail.cc> | 2024-02-27 22:18:12 +0000 |
| commit | f0a6578259f508a8863afcf9a1487872d7ae1878 (patch) | |
| tree | f82cdd918621744a9c7e509079efa40737cea6b0 /video/out/wayland_common.h | |
| parent | 34c0a67ace7c0dcc8c53ee2ca1879135add4dc7d (diff) | |
| download | mpv-f0a6578259f508a8863afcf9a1487872d7ae1878.tar.bz2 mpv-f0a6578259f508a8863afcf9a1487872d7ae1878.tar.xz | |
wayland: drop buffer scale for cursor as well
Could have been done in e32554cd570d984efb712a7214a40237233a3cea, but I
skipped it there. However, using viewporter is actually a win here.
There's been a longstanding issue in upstream wayland* exactly related
to this. I even forgot about cd7a7a1de8d8bffa05170befef25b251711c994a
which was made for this exactly problem and explains the random
spawn_cursor calls. Anyways, just not using buffer scale and instead
scaling the cursor surface via viewporter works just fine and completely
sidesteps this problem. This means we can drop the random looking
spawn_cursor calls and some additional checks.
*: https://gitlab.freedesktop.org/wayland/wayland/-/issues/194
Diffstat (limited to 'video/out/wayland_common.h')
| -rw-r--r-- | video/out/wayland_common.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/video/out/wayland_common.h b/video/out/wayland_common.h index f45c732ee1..845632d06f 100644 --- a/video/out/wayland_common.h +++ b/video/out/wayland_common.h @@ -133,6 +133,7 @@ struct vo_wayland_state { /* viewporter */ struct wp_viewporter *viewporter; struct wp_viewport *viewport; + struct wp_viewport *cursor_viewport; struct wp_viewport *osd_viewport; struct wp_viewport *video_viewport; |