From e7d0a0b0ed4f61ce8fbddc0a49a95f04e0959be4 Mon Sep 17 00:00:00 2001 From: Rob Bradford Date: Wed, 17 Apr 2013 18:28:42 +0100 Subject: [PATCH] protocol: Make it clear that returned "one-shot" objects are destroyed The objects returned by the frame and sync request are destroyed by the compositor after the "done" event on the wl_callback interface is fired. --- protocol/wayland.xml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/protocol/wayland.xml b/protocol/wayland.xml index eda94410..edb8a034 100644 --- a/protocol/wayland.xml +++ b/protocol/wayland.xml @@ -40,6 +40,10 @@ handled in-order and events are delivered in-order, this can used as a barrier to ensure all previous requests and the resulting events have been handled. + + The object returned by this request will be destroyed by the + compositor after the callback is fired and as such the client must not + attempt to use it after that point. @@ -972,6 +976,10 @@ damage, or any other state changes. wl_surface.commit triggers a display update, so the callback event will arrive after the next output refresh where the surface is visible. + + The object returned by this request will be destroyed by the + compositor after the callback is fired and as such the client must not + attempt to use it after that point.