On Thu, 16 May 2013 15:49:35 +0200 [email protected] wrote: > From: Alexander Larsson <[email protected]> > > This add a wl_output.done event which is send after every group > of events caused by some property change. This allows clients to treat > changes touching multiple events in an atomic fashion.
Hi, why did you end up deciding that this is better than using the geometry event as the end signal? Thanks, pq > --- > protocol/wayland.xml | 12 +++++++++++- > 1 file changed, 11 insertions(+), 1 deletion(-) > > diff --git a/protocol/wayland.xml b/protocol/wayland.xml > index 3bce022..d3ae149 100644 > --- a/protocol/wayland.xml > +++ b/protocol/wayland.xml > @@ -1467,7 +1467,7 @@ > </event> > </interface> > > - <interface name="wl_output" version="1"> > + <interface name="wl_output" version="2"> > <description summary="compositor output region"> > An output describes part of the compositor geometry. The > compositor works in the 'compositor coordinate system' and an > @@ -1565,6 +1565,16 @@ > <arg name="height" type="int" summary="height of the mode in pixels"/> > <arg name="refresh" type="int" summary="vertical refresh rate in mHz"/> > </event> > + > + <event name="done" since="2"> > + <description summary="sent all information about output"> > + This event is sent after all other properties has been > + sent after binding to the output object and after any > + other property changes done after that. This allows > + changes to the output properties to be seen as > + atomic, even if they happen via multiple events. > + </description> > + </event> > </interface> > > <interface name="wl_region" version="1"> _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
