Re: [PATCH wayland v2] protocol: try to clarify frame callback semantics

2014-02-22 Thread Pekka Paalanen
On Fri, 21 Feb 2014 10:53:03 -0800 Bill Spitzak wrote: > How about something like this, which is my understanding: > > "The frame callback is sent when it is known that the last commit will > be visible on the screen. If a second commit is sent before the frame > callback it is quite possible

Re: [PATCH wayland v2] protocol: try to clarify frame callback semantics

2014-02-22 Thread Pekka Paalanen
On Fri, 21 Feb 2014 21:38:15 -0600 Jason Ekstrand wrote: > Pekka, > Sorry this e-mail took so long to send. Not much time lately. The first > time or two I read this suggested re-wording I didn't like it, but now it's > starting to grow on me. I still kind of like the idea of "the buffer you >

Re: [PATCH wayland v2] protocol: try to clarify frame callback semantics

2014-02-22 Thread Pekka Paalanen
Hi, thanks for all the comments, it's encouraging to see a concensus emerging. One reply below... On Sat, 22 Feb 2014 07:50:01 -0600 Jason Ekstrand wrote: > On Feb 22, 2014 2:44 AM, "Axel Davy" wrote: > > > > Hi, > > > > I like very much the rewording proposed by Pekka. > > > > But I dislike y

Re: [PATCH libinput 2/2] Hook up event processing to libevdev

2014-02-22 Thread Jonas Ådahl
On Tue, Feb 18, 2014 at 04:09:10PM +1000, Peter Hutterer wrote: > This gives us the ability to handle SYN_DROPPED transparently to the caller. > > Signed-off-by: Peter Hutterer > --- > src/evdev.c | 90 > +++-- > 1 file changed, 58 inserti

Re: [PATCH libinput 1/2] Hook up libevdev as backend

2014-02-22 Thread Jonas Ådahl
On Tue, Feb 18, 2014 at 04:09:09PM +1000, Peter Hutterer wrote: > libevdev wraps the various peculiarities of the evdev kernel API into a > type-safe API. It also buffers the device so checking for specific features at > a later time is easier than re-issuing the ioctls. Plus, it gives us almost >

[PATCH libinput] test: Add seat slot tests

2014-02-22 Thread Jonas Ådahl
Add one test that checks uniqueness of seat slots when having multiple devices with active touch points. Add one test that checks that libinput drops touch points when it could not represent them with a seat wide slot. This commit also adds support for from a test case add test devices to an exis

[PATCH libinput v2] Add seat wide slot to touch events

2014-02-22 Thread Jonas Ådahl
Since a Wayland compositor have to represent all touch devices of a seat as one virtual device, lets make that easier by also providing seat wide slots with touch events. Seat wide slots may be accessed using libinput_event_touch_get_seat_slot(). Signed-off-by: Jonas Ådahl --- Changes since v1:

Re: [PATCH wayland v2] protocol: try to clarify frame callback semantics

2014-02-22 Thread Jason Ekstrand
On Feb 22, 2014 2:44 AM, "Axel Davy" wrote: > > Hi, > > I like very much the rewording proposed by Pekka. > > But I dislike your proposition to send frame callbacks right away if the attached buffer has been attached for a long time. > > Your argument seems to be that the client may manage to get

Re: [RFC] libinput configuration interface

2014-02-22 Thread Alexander E. Patrakov
2014-02-21 5:26 GMT+06:00 Peter Hutterer : > On Fri, Feb 21, 2014 at 01:29:05AM +0600, Alexander E. Patrakov wrote: >> Vertical two-finger scrolling works, but is way too sensitive both >> with constant deceleration 1.0 and with 0.3. > > that's a xf86-input-libinput bug, Benjamin fixed that but I f

Re: [PATCH wayland v2] protocol: try to clarify frame callback semantics

2014-02-22 Thread Axel Davy
Hi, I like very much the rewording proposed by Pekka. But I dislike your proposition to send frame callbacks right away if the attached buffer has been attached for a long time. Your argument seems to be that the client may manage to get to the next pageflip if the frame callback is called r