Hi,
On 25 May 2015 at 20:15, Rui Matos 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 th
This makes sense to me.
Reviewed-by: Jasper St. Pierre
On Mon, May 25, 2015 at 12:15 PM, Rui Matos 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, us
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.
Signed-off-by: Rui Matos
---
hw/xwayland/xway
