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 tiagoma...@gmail.com
Rui Matos tiagoma...@gmail.com 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.
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 tiagoma...@gmail.com
Hi,
On 26 May 2015 at 16:37, 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
Daniel Stone dan...@fooishbar.org writes:
Signed-off-by: Rui Matos tiagoma...@gmail.com
Thanks!
Reviewed-by: Daniel Stone dani...@collabora.com
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
