Re: [RFC wayland-protocols] unstable: Add input-timestamps protocol

2017-11-30 Thread Alexandros Frantzis
On Thu, Nov 30, 2017 at 04:08:06PM +1000, Peter Hutterer wrote: > On Wed, Nov 29, 2017 at 12:42:57PM +0200, Alexandros Frantzis wrote: > > wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit > > timestamp with millisecond resolution. In some cases, notably latency > > measurements, t

Re: [RFC wayland-protocols] unstable: Add input-timestamps protocol

2017-11-29 Thread Peter Hutterer
On Wed, Nov 29, 2017 at 12:42:57PM +0200, Alexandros Frantzis wrote: > wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit > timestamp with millisecond resolution. In some cases, notably latency > measurements, this resolution is too coarse to be useful. > > This protocol provides a

[RFC wayland-protocols] unstable: Add input-timestamps protocol

2017-11-29 Thread Alexandros Frantzis
wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit timestamp with millisecond resolution. In some cases, notably latency measurements, this resolution is too coarse to be useful. This protocol provides additional timestamps events, which are emitted just before the corresponding in