Rui Matos writes:
> 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
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
---
On Tue, May 26,
Daniel Stone writes:
>> Signed-off-by: Rui Matos
>
> Thanks!
>
> Reviewed-by: Daniel Stone
>
> Keith, please pull.
Looks like there have been some other updates in this area? Can I get
one of you to build a patch on master?
--
-keith
signature.asc
Description: PGP signature
___
Hi,
On 26 May 2015 at 16:37, 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
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
---
v2: ensure that
