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

2017-12-18 Thread Pekka Paalanen
On Mon, 18 Dec 2017 13:53:28 +0200 Alexandros Frantzis wrote: > On Mon, Dec 18, 2017 at 12:50:30PM +0200, Pekka Paalanen wrote: > > On Wed, 13 Dec 2017 16:48:28 +0200 > > Alexandros Frantzis wrote: > > > > > On Mon, Dec 11, 2017 at 03:25:28PM +0200, Pekka Paalanen wrote: > > > > On Tue, 5

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

2017-12-18 Thread Alexandros Frantzis
On Mon, Dec 18, 2017 at 12:50:30PM +0200, Pekka Paalanen wrote: > On Wed, 13 Dec 2017 16:48:28 +0200 > Alexandros Frantzis wrote: > > > On Mon, Dec 11, 2017 at 03:25:28PM +0200, Pekka Paalanen wrote: > > > On Tue, 5 Dec 2017 18:07:02 +0200 > > > Alexandros Frantzis wrote: > > > > > > > wl_po

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

2017-12-18 Thread Pekka Paalanen
On Wed, 13 Dec 2017 16:48:28 +0200 Alexandros Frantzis wrote: > On Mon, Dec 11, 2017 at 03:25:28PM +0200, Pekka Paalanen wrote: > > On Tue, 5 Dec 2017 18:07:02 +0200 > > Alexandros Frantzis wrote: > > > > > wl_pointer, wl_keyboard and wl_touch events currently use a 32-bit > > > timestamp wi

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

2017-12-17 Thread Jonas Ådahl
On Tue, Dec 05, 2017 at 06:07:02PM +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

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

2017-12-13 Thread Alexandros Frantzis
On Mon, Dec 11, 2017 at 03:25:28PM +0200, Pekka Paalanen wrote: > On Tue, 5 Dec 2017 18:07:02 +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, th

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

2017-12-11 Thread Pekka Paalanen
On Tue, 5 Dec 2017 18:07:02 +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 additi

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

2017-12-11 Thread Pekka Paalanen
On Tue, 5 Dec 2017 18:20:35 +0200 Alexandros Frantzis wrote: > On Tue, Dec 05, 2017 at 06:07:02PM +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, th

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

2017-12-07 Thread Peter Hutterer
On Tue, Dec 05, 2017 at 06:07:02PM +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

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

2017-12-05 Thread Alexandros Frantzis
On Tue, Dec 05, 2017 at 06:07:02PM +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

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

2017-12-05 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 high-resolution timestamps events, which are emitted before the corre