diff options
| author | Pekka Paalanen <ppaalanen@gmail.com> | 2012-10-11 14:31:11 +0300 |
|---|---|---|
| committer | Kristian Høgsberg <krh@bitplanet.net> | 2012-10-11 09:58:28 -0400 |
| commit | eb5fae3226fa6d0c542fda54a35e282466167e96 (patch) | |
| tree | f8c59061594b76975446456e88162bb25894af2f /protocol | |
| parent | 0a27ce1fc2b76b5f50451d7e7c76f97a7056615d (diff) | |
protocol: clarify multiple wl_surface.attach
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>
Diffstat (limited to 'protocol')
| -rw-r--r-- | protocol/wayland.xml | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/protocol/wayland.xml b/protocol/wayland.xml index 275ea28..07fee80 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -678,7 +678,9 @@ time after the wl_surface.commit request. When the compositor will not access the pixels anymore, it will send the wl_buffer.release 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 surface contents, even if the wl_buffer is still pending for the |