Simon Ser 3e897faa29 protocol: allow immediate wl_buffer.destroy if not re-used ... Allow wl_buffer objects to be destroyed without having to wait for wl_buffer.release if the underlying storage isn't going to be re-used. The main motivation for this is to avoid glitches when a client is torn down. When a client disconnects, all of its objects are destroyed in arbitrary order. However some compositors will still need to access the destroyed buffer's underlying storage afterwards, e.g. for visual effects (fade-out) or for atomic layout updates (wait for other clients to commit a new buffer before hiding the buffer). It's still incorrect for clients to destroy a wl_buffer and mutate the underlying storage without waiting for wl_buffer.release. Signed-off-by: Simon Ser <contact@emersion.fr> Closes: https://gitlab.freedesktop.org/wayland/wayland/-/issues/185		2021-06-11 14:05:27 +00:00
..
.gitignore	Update .gitignore for protocol/	2013-11-19 13:26:04 -08:00
generate-shm-formats.py	Add an automated script to update wl_shm.format	2019-09-06 12:09:22 +00:00
tests.xml	Replace initial 8 spaces with a tab for all xml files	2020-04-29 12:21:33 +00:00
wayland.dtd	protocol: Add type attribute to events	2021-01-27 17:49:10 +00:00
wayland.xml	protocol: allow immediate wl_buffer.destroy if not re-used	2021-06-11 14:05:27 +00:00