mirrors/wayland
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland.git synced 2025-11-25 06:59:46 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions

protocol: clarify multiple wl_surface.attach

Browse source 
Explicitly say what happens with the wl_buffer.release event, if you
attach several wl_buffers without a commit in between.

Reported-by: David Herrmann <dh.herrmann@googlemail.com>
Signed-off-by: Pekka Paalanen <ppaalanen@gmail.com>
This commit is contained in:
Pekka Paalanen 2012-10-11 14:31:11 +03:00 • committed by Kristian Høgsberg
parent 0a27ce1fc2
commit eb5fae3226
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
protocol/wayland.xml
View file

@ -678,7 +678,9 @@
time after the wl_surface.commit request. When the compositor will time after the wl_surface.commit request. When the compositor will
not access the pixels anymore, it will send the wl_buffer.release not access the pixels anymore, it will send the wl_buffer.release
event. Only after receiving wl_buffer.release, the client may re-use event. Only after receiving wl_buffer.release, the client may re-use
the wl_buffer. the wl_buffer. A wl_buffer, that has been attached and then replaced
by another attach instead of committed, will not receive a release
event, and is not used by the compositor.
Destroying the wl_buffer after wl_buffer.release does not change the Destroying the wl_buffer after wl_buffer.release does not change the
surface contents, even if the wl_buffer is still pending for the surface contents, even if the wl_buffer is still pending for the