Hi, On 25 May 2015 at 20:15, Rui Matos <tiagoma...@gmail.com> wrote: > In some extreme cases with animated cursors at a high frame rate we > could end up filling the wl_display outgoing buffer and end up with > wl_display_flush() failing. > > In any case, using the frame callback to throttle ourselves is the > right thing to do.
I agree, but it seems like this will lose updates posted when set_cursor is awaiting a callback. I think the early-return case should stash the pending values, and the frame callback should post & clear the pending values. Cheers, Daniel _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
