- Mar 08, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If a touch started hovering in the main area, the button state would start with AREA and never move to the real button state, despite the finger triggering the pressure thresholds correctly in one of the areas. This could even happen across touch sequences if a touch went below pressure in the software button area, it changed to hovering and the button state changed to NONE. On the next event, the touch is still hovering and the current position of the touch is taken for the button state machine. https://bugs.freedesktop.org/show_bug.cgi?id=99976 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> (cherry picked from commit c0dbd6eb)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 07ce6c89)
-
Peter Hutterer authored
Introduced in commit 8e7f99c2 we only allowed horizontal edge scrolling on devices larger than 50mm to leave enough reactive space on the touchpad. Looking at a ruler, a 50mm high touchpad is still large enough to leave the bottom 7mm as an horizontal edge scroll area. Reduce the minimum size to 40mm instead, that's closer to where it starts to get a bit iffy. https://bugzilla.redhat.com/show_bug.cgi?id=1422221 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> (cherry picked from commit d6379bc3)
-
- Feb 27, 2017
-
-
Peter Hutterer authored
We don't cater for the special case of groups having a different number of modes, there is no hardware right now that does that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> (cherry picked from commit 38c675c9)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> (cherry picked from commit c787ccf2)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit d248049f)
-
- Feb 21, 2017
-
-
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> (cherry picked from commit c5d9ecbd)
-
Peter Hutterer authored
Missing from 8c1aa1de where we hid the human-readable parts but the keycode itself is still enough information to recover the typed bits. Print it as -1 as that keycode doesn't exist for real keys so it stands out nicely. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit a6b550cb)
-
Peter Hutterer authored
libinput-debug-events prints keycodes as they come in. This makes it dangerous to be run by users (especially in the background) because it will leak sensitive information as it is typed. Obfuscate the base set of keycodes by default, require a --show-keycodes switch to show it. The few times we actually need the keycodes, we can run the switch in the debugging tool. This does not affect keys outside of the main block on the keyboard (F-keys, multimedia keys). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com> (cherry picked from commit 8c1aa1de)
-
- Feb 17, 2017
-
-
Peter Hutterer authored
We don't initialize click methods on devices with physical buttons. This model is a special case, it's not a clickpad but it only has one button (because one button is all you ever need and whatnot). https://bugs.freedesktop.org/show_bug.cgi?id=99283 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit f2f616a1)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit a04ba9a2)
-
- Feb 16, 2017
-
-
Peter Hutterer authored
We don't init the required /sysfs files, so let's not spew a lot of warnings during the test suite. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit df18c6b1)
-
Peter Hutterer authored
42 and 58 were within the middle button already, 40/60 are more accurate values. https://bugs.freedesktop.org/show_bug.cgi?id=99212 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit cbe9a3bf)
-
- Feb 02, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The timeout is too short, a number of users are unable to tap now. https://bugs.freedesktop.org/show_bug.cgi?id=99447 This reverts commit d0ba1e2b. (cherry picked from commit e86fdd58)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit ab563d09)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit a5cefb76)
-
Peter Hutterer authored
For each device open the various led devices (brightness only) and map the one nonzero brightness to the current mode. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 5eb71b65)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 9672e2f4)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit aae997e6)
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 13a2336b)
-
Peter Hutterer authored
Loop immediately exited, this code was never triggered. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> (cherry picked from commit 4d20130e)
-
- Jan 19, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When the filter code switched to raw device coordinates (bdd4264d) the input data remained in device coordinates. Since the factor for touchpads was still based on the physical velocity (and thus all touchpads get the same acceleration factor for identical moves), the actual delta was dependent on the resolution. e.g. touchpad with 40u/mm: delta of 2/2 * accel factor 2 -> accel delta of 4/4 touchpad with 20u/mm: delta of 1/1 * accel factor 2 -> accel delta of 2/2 The normalized coordinates should be independent of the touchpad's resolution though. Affected by this was the standard mouse accel code and the touchpad accel code, other filters always returned unnormalized coordinates (separate bug, not addressed here). This patch restores the correct behaviour for mice and touchpads while leaving the special filters untouched. For comparision: * 1000+dpi mice: accelerate normalized, return normalized * touchpads: accelerate unnormalized, return normalized * low-dpi mice: accelerate unnormalized, return unnormalized * trackpoints: accelerate unnormalized, return unnormalized * x230: don't touch, already does the right thing https://bugs.freedesktop.org/show_bug.cgi?id=99383 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 18, 2017
-
-
Peter Hutterer authored
We were just switching type here without actual normalization, the filter code is in device units as of bdd4264d. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Jan 17, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Fallout from 5d66edc9 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Signed-off-by: Rohith Mukku <rohithmukku@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 16, 2017
-
-
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>
-
Peter Hutterer authored
From systemd commit f644a6da7a: "pyparsing 2.1.10 fixed the handling of LineStart to really just apply to line starts and not ignore whitespace and comments any more. Adjust EMPTYLINE to this." Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Use the model names in the file name and append pad/pen/finger as appropriate Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
I'm using semaphore CI for build testing and that only provides Ubuntu 14.04 which doesn't have libevdev 1.3 or later. Since this is a minor workaround for an error case only, revert the commit again and leave the handling in. Less effort than having to patch around it in semaphore. This reverts commit 1e0736da.
-
- Jan 15, 2017
-
-
Peter Hutterer authored
gcov analysis showed that none of the actual testing conditions were hit, so the test succeeded despite not actually testing anything. Which is good, because testing for tilt normalization isn't correct anyway, tilt is in physical degrees, Drop the test and replace it with a test for pressure normalization instead. We already have a similar one to check for [0, 1] range, this new one explicitly tests for the extents. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This isn't true anymore with kernel 4.5 and libevdev 1.5.0 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
1.3 has been out since Sep 2014, that's enough time. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Don't access the struct until we've verified it is what we want. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
They weren't originally prefixed but the various tests were, but now that we only have one test runner binary anyway, the prefix helps sorting the files easily within e.g. gcov results. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-