On Fri, 22 Aug 2014 11:35:40 +0300 Pekka Paalanen <ppaala...@gmail.com> wrote:
> On Thu, 21 Aug 2014 09:08:56 -0700 > Jason Ekstrand <ja...@jlekstrand.net> wrote: > > > That applies to the whole series, BTW > > > > > > On Thu, Aug 21, 2014 at 9:03 AM, Jason Ekstrand <ja...@jlekstrand.net> > > wrote: > > > > > LGTM > > > Reviewed-by: Jason Ekstrand <jason.ekstr...@intel.com> > > Thank you, Jason. :-) > > Jasper already acked this in irc, but I would like to get an official > R-b, too. > > Then, once we have an implementation for Weston, I can land this. Quite > likely it means after 1.6.0, though, unless I can whip it up today... > quite probably I won't have the time for that, though. This series has now landed in master. I'll start sketching the alternative to Jasper's suggestion for enforcing this in Weston and where the error codes should live. Thanks, pq > > > On Thu, Aug 21, 2014 at 2:52 AM, Pekka Paalanen > > > <ppaala...@gmail.com> wrote: > > > > > >> From: Pekka Paalanen <pekka.paala...@collabora.co.uk> > > >> > > >> Define what a role is, and what restrictions there are. > > >> > > >> A change to existing behaviour is that a role cannot be changed at > > >> all once set. However, this is unlikely to cause problems, as > > >> there is no reason to re-use wl_surfaces in clients. > > >> > > >> v2: give more concrete examples of roles, define losing a role, > > >> Jasper rewrote the paragraph on how a role is set. > > >> > > >> v3: make role permanent, there is no such thing as "losing a role". > > >> Re-issuing the same role again must be allowed for > > >> wl_pointer.set_cursor et al. to work. > > >> > > >> v4: clarify the semantics of destroying a role object. > > >> > > >> Signed-off-by: Pekka Paalanen <pekka.paala...@collabora.co.uk> > > >> --- > > >> protocol/wayland.xml | 33 +++++++++++++++++++++++++++++++-- _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
