[libinput] How can I prevent duplicated device?

Hello, guys. I have a one question about the libinput API. I want to share your opinions about duplicated device added events via udev. Suppose to duplicated device add events(about a same device) are occurred. Currently libinput opens two fd about a same event node. So that I have a question

Re: [RFC wayland-web] docs, web site, logo

On Mon, Aug 22, 2016 at 12:37:52PM +0300, Pekka Paalanen wrote: > On Sat, 20 Aug 2016 11:54:29 +0100 > Daniel Stone wrote: > > > Hi Yong, > > > > On 19 August 2016 at 20:08, Yong Bakos wrote: > > > Hi everyone, > > > This may feel a bit trivial but

Re: [RFC wayland-web] docs, web site, logo

Hi On Mon, Aug 22, 2016 at 11:37 AM, Pekka Paalanen wrote: > On Sat, 20 Aug 2016 11:54:29 +0100 > Daniel Stone wrote: > > [...] > >> I think this is easily the lowest-priority issue here. It's not the >> best, but it certainly works, and it's not

Re: [RFC wayland-web] docs, web site, logo

On Sat, 20 Aug 2016 11:54:29 +0100 Daniel Stone wrote: > Hi Yong, > > On 19 August 2016 at 20:08, Yong Bakos wrote: > > Hi everyone, > > This may feel a bit trivial but I would like to get a sense of how some > > improvements to the documentation,

[PATCH libinput 5/6] test: move the Intuos 5 and Cintiq 13HD test tablets into the same device group

Signed-off-by: Peter Hutterer --- test/litest-device-wacom-cintiq-13hdt-finger.c | 10 ++ test/litest-device-wacom-cintiq-13hdt-pad.c| 3 ++- test/litest-device-wacom-cintiq-13hdt-pen.c| 10 ++ test/litest-device-wacom-intuos-finger.c | 10

[PATCH libinput] touchpad: reset the edge scroll state on touch up if edge scroll is disabled

If a touch was down (and up again) before the device was switched to edge scrolling, libinput reported an error message: litest error: libinput bug: unexpected scroll event 0 in area state While edge scrolling was disabled, any new touch would be set to the area state but it was never reset on

[PATCH libinput 3/6] evdev: don't send frame events if we filtered the touch event

If the touch is inactive the seat_slot is -1 and we filter the event. The same happens for devices that send may touch events but aren't touch devices like any touch-capable mouse. In those cases we sent a bunch of 'empty' touch frame events. Stop this by checking if we actually flushed the

[PATCH libinput 4/6] evdev: release current touches when the device is suspended

Previously suspending a touch device with at least one touch down would never release the touch point. Signed-off-by: Peter Hutterer --- src/evdev.c | 39 +++- test/device.c | 83 +++ 2