On 8 July 2013 17:25, Jason Ekstrand <[email protected]> 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? Rob _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
