- Nov 11, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Nov 09, 2016
-
-
Signed-off-by:
Hermann Gausterer <git-libinput-2016@mrq1.org> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Nov 04, 2016
-
-
Peter Hutterer authored
Not all mice have a click angle with integer degrees. The new MOUSE_WHEEL_CLICK_COUNT property specifies how many clicks per full rotation, the angle can be calculated from that. See https://github.com/systemd/systemd/pull/4440 for more information CLICK_COUNT overrides CLICK_ANGLE, so we check for the former first and then fall back to the angle if need be. No changes to the user-facing API. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Nov 03, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Nov 02, 2016
-
-
Peter Hutterer authored
Same as the HP Compat 8510, it doesn't send BTN_TOOL_DOUBLETAP/TRIPLETAP. This may be a general issue with those series but they're 6 years old now, so it's questionable to spend extra effort detecting them. https://bugs.freedesktop.org/show_bug.cgi?id=98538 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
A joystick has ID_INPUT_JOYSTICK *and* ID_INPUT set, so we need to check for both. https://bugs.freedesktop.org/show_bug.cgi?id=98009 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Nov 01, 2016
-
-
Peter Hutterer authored
upstream for this file lives in systemd, any changes to the actual parser should flow back there. libinput's matches are fairly simple. We have the various LIBINPUT_MODEL_ tags that just take a "1" and the two attributes that are dimensions. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Oct 28, 2016
-
-
Peter Hutterer authored
No functional changes Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
No functional changes, just to filter out devices that don't match immediately. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
No functional changes Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Oct 25, 2016
-
-
Peter Hutterer authored
Without the comma it now assigns the horizontal click angle property to all devices. Introduced in b02acd34 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
To be expanded at some future time... Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
Eric Engestrom <eric.engestrom@imgtec.com>
-
Peter Hutterer authored
silence clang warning: evdev-mt-touchpad.c:1017:7: warning: using floating point absolute value function 'fabs' when argument is of integer type [-Wabsolute-value] Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
Eric Engestrom <eric.engestrom@imgtec.com>
-
Peter Hutterer authored
Fixes the respective clang warnings Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
Eric Engestrom <eric.engestrom@imgtec.com>
-
- Oct 19, 2016
-
-
Peter Hutterer authored
Split it into several device-specific sections Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 15, 2016
-
-
This makes it clear that it's not meant to be dereferenced. CC: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by:
Eric Engestrom <eric.engestrom@imgtec.com> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 14, 2016
-
-
Peter Hutterer authored
freedesktop.org always serves https for the documentation. if Mathjax is pulled in from http, browsers reject it [1] Let's take the default doxygen value but just add the https to it. In the future we should just ship a copy of mathjax with our documentation. [1] https://developer.mozilla.org/en-US/docs/Web/Security/Mixed_content/How_to_fix_website_with_mixed_content Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Wheres-my-beer-by:
Yong Bakos <ybakos@humanoriented.com> Reviewed-by:
Yong Bakos <ybakos@humanoriented.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
prefix must be libinput, not evdev Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 12, 2016
-
-
Peter Hutterer authored
Some trackpoints, notably the one on the Lenovo T460s have a tendency to send the odd event even when they're not actually used. Trackpoint events trigger palm detection (see 0210f1fe) and thus effectively disable the touchpad, causing the touchpad to appear nonresponsive. Fix this by requiring at least 3 events from a trackpoint before palm detection is enabled. For normal use it's hard enough to trigger a single event anyway so this should not affect the normal use-case. https://bugzilla.redhat.com/show_bug.cgi?id=1364850 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Sep 09, 2016
-
-
Peter Hutterer authored
That's where this device comes from. The x220 is special because it's too small to trigger some of the features, eg. palm detection. Make this more obvious by changing to a less generic name. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 08, 2016
-
-
Peter Hutterer authored
We print the sysname, but it's not always obvious when there's an event from another device within the stream from another device. Prefix it so it's easier to spot and search for. See https://bugzilla.redhat.com/show_bug.cgi?id=1364850#c3 for an example of how such an event can hide. We only use last_device for comparing pointer values so we don't need a reference to the device, it doesn't matter if the device itself goes out of scope. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 07, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
INPUT_PROP_BUTTONPAD is not set on this device and RMI4 which should fix this is a bit too far into the future at this point. Hack around it. https://bugs.freedesktop.org/show_bug.cgi?id=97147 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
So far we've relied on the wacom kernel module to do touch arbitration for us but that won't be the case in upcoming kernels. Implement touch arbitration in userspace by pairing the two devices and suspending the touch device whenever a tool comes into proximity. In the future more sophisticated arbitration can be done (e.g. only touches which are close to the pen) but let's burn that bridge when we have to cross it. Note that touch arbitration is "device suspend light", i.e. we leave the device enabled and the fd is active. Tablet interactions are comparatively short-lived, so closing the fd and asking logind for a new one every time the pen changes proximity is suboptimal. Instead, we just keep a boolean around and discard all events while it is set. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
No functional changes. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
Touch sequences are interrupted by TOUCH_FRAME events which makes them annoying to handle event-by-event. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
Previously suspending a touch device with at least one touch down would never release the touch point. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
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 respective event. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
Rather than testing before if we have an event that matches the need for a frame simply return the event sent by the flush function. If that event matches those that need frame events, send the event then. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
Peter Hutterer authored
No functional changes, this is prep work for being able to release touch points on the fly. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jason Gerecke <jason.gerecke@wacom.com>
-
- Sep 06, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 05, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Sep 04, 2016
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
-