[PATCH] Allow null surface arguments in wl_pointer.leave and wl_keyboard.leave

Rob Bradford robert.bradford at intel.com
Mon Jul 8 09:32:09 PDT 2013

On 8 July 2013 17:25, Jason Ekstrand <jason at jlekstrand.net> wrote:

> That's exactly what weston *was* doing.  However, thanks to the destroyed
> proxies, the clients were getting NULL anyway.  We could to go through a
> bunch of trouble to keep the resource valid and call wl_pointer.leave on a
> valid resource.  However, that's a lot more work than I thought it was worth
> for no change client-side.

Right - you spell this out nice and clearly in your excellent commit
message. So although this is technically an API change all the clients
already deal with this anyway - so I guess it's right to spell that
out in the protocol.

Out of interest - when does the compositor emit a motion event without
a resource?


More information about the wayland-devel mailing list