[PATCH wayland] protocol: Make it clear that returned "one-shot" objects are destroyed

[Kristian Høgsberg]

On Wed, Apr 17, 2013 at 06:28:42PM +0100, Rob Bradford wrote:
> From: Rob Bradford <rob at linux.intel.com>
> 
> 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(+)

Ah, I remember we talked about that.  Thanks, applied.

Kristian

> diff --git a/protocol/wayland.xml b/protocol/wayland.xml
> index 9d71c23..023067a 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.
>        </description>
>        <arg name="callback" type="new_id" interface="wl_callback"/>
>      </request>
> @@ -1012,6 +1016,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.
>        </description>
>  
>        <arg name="callback" type="new_id" interface="wl_callback"/>
> -- 
> 1.8.1.4
> 
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel