On Wed, 4 Mar 2015 14:30:41 -0600
Derek Foreman wrote:
> It's useful to know how long the current cursor frame should be displayed
> so we can wait that long to change it.
>
> Signed-off-by: Derek Foreman
> ---
> differences from v1:
> Add comment about 0 durations
> document return of 0 dur
It's useful to know how long the current cursor frame should be displayed
so we can wait that long to change it.
Signed-off-by: Derek Foreman
---
differences from v1:
Add comment about 0 durations
document return of 0 duration as unchanging image
make sure duration calculation doesn't wrap aro
On 04/03/15 01:50 AM, Pekka Paalanen wrote:
> On Tue, 3 Mar 2015 15:24:13 -0600
> Derek Foreman wrote:
>
>> It's useful to know how long the current cursor frame should be displayed
>> so we can wait that long to change it.
>>
>> Signed-off-by: Derek Foreman
>> ---
>>
>> In a follow up weston p
On Tue, 3 Mar 2015 15:24:13 -0600
Derek Foreman wrote:
> It's useful to know how long the current cursor frame should be displayed
> so we can wait that long to change it.
>
> Signed-off-by: Derek Foreman
> ---
>
> In a follow up weston patch I use this to let toytoolkit set the cursor
> with
It's useful to know how long the current cursor frame should be displayed
so we can wait that long to change it.
Signed-off-by: Derek Foreman
---
In a follow up weston patch I use this to let toytoolkit set the cursor
with a timerfd instead of using a frame callback.
cursor/wayland-cursor.c |
