Simon Ser f620b32dc3 backend/wayland: allow superseding a previous commit ... During a modeset, the core wlr_output logic will allocate a buffer with a new size and commit it. However if we still have a frame callback pending we'd refuse to perform the commit. This is inconsistent with the DRM backend, which performs a blocking modeset. This is visible when resizing the Wayland toplevel. The logs are filled with "Skipping buffer swap", and the wlr_damage_ring's bounds are not properly updated. Fix this by destroying the pending frame wl_callback. (cherry picked from commit 2e49fa1a0a)		2023-02-02 19:01:43 +01:00
..
backend.c	backend/wayland: don't cache next item when destroying buffers	2023-02-02 17:53:10 +01:00
meson.build	backend/wayland: give wlr_pointer ownership to wlr_wl_seat	2022-03-17 17:16:47 +00:00
output.c	backend/wayland: allow superseding a previous commit	2023-02-02 19:01:43 +01:00
pointer.c	Use wl_signal_emit_mutable	2022-08-18 07:16:16 -04:00
seat.c	Use wl_signal_emit_mutable	2022-08-18 07:16:16 -04:00
tablet_v2.c	Use wl_signal_emit_mutable	2022-08-18 07:16:16 -04:00