- Mar 14, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Available as 'libinput test-suite'. This also renames the bit in the build directory now. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This allows us to run the test suite runner against the installed system rather than always using the build tree quirks. The actual option will be removed in a future commit, it is just here for commit consistency and testing. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We want to use this from the tests as well soon, so let's move it to a more generic location. This also changes the API to be slightly more sensible, a free() is the same cost (and safer) than passing a static buffer in and hoping we didn't get the size wrong. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
All the bits that test for utility functions to work correctly can be run separately from the main test suite (which tests devices and libinput in general). These bits here are the ones that test the code itself and aren't reliant on anything else. 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
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
No functional changes Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
It's a one-liner, we don't need this as a separate file. Plus, this makes the test suite runner less dependent on the build directory. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
These don't need to be in the libinput config.h Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 12, 2019
-
-
Peter Hutterer authored
We don't want to valgrind through python... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If more than 255 tests fail, we're returning an exit code outside of the POSIX standard. This only takes effect for -j1, where we fork off we only ever have a failed value of 1 anyway. 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
Running the test suite runner is good, but not sufficient, a full ninja test is required to get the full coverage. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
With meson this is now in the build directory Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 06, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 04, 2019
-
-
Peter Hutterer authored
Draw a second smaller scroll bar that moves with every discrete step. For that to work, we have to accumulate the value from the normal scroll events until we get the first discrete one, then move up. The value per discrete event changes depending on the click wheel angle, so we can't just use discrete on its own if we want the two scroll bars aligned. 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
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
When exiting RELEASE_DELAYED state, do not transition into states to detect the need for spurious mode (RELEASE_WAITING, MAYBE_SPURIOUS). RELEASE_DELAYED is only entered when spurious mode is enabled, there is no need to detect the need for spurious mode again.
-
- Feb 19, 2019
-
-
When using button scrolling, a hardcoded delay of 200 milliseconds between button down and scroll events being emitted makes fast scrolling gestures feel clunky and sometimes fail entirely. This feature comes from xf86-input-mouse, was copied into xf86-input-evdev and reimplemented in libinput. This was, as far as can be determined, to allow right clicks without triggering scrolling. libinput now also has distance triggers (2bbf4a01) and sends button events if no movement has happened for long clicks, regardless of the delay. The 200ms delay is thus not really necessary anymore, let's drop it to 38ms which is just above the 3-event threshold for 8/10/12ms intervals which is most devices. Fixes #237 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 18, 2019
-
-
Peter Hutterer authored
Fixes #220 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 14, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Found by coverity Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
When the loop was reduced to BTN_DIGI only, it guaranteed that the BTN_STYLUS condition was no longer met. Found by coverity Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Diep Pham authored
-
Peter Hutterer authored
The latter has more obvious handling of hwdb matches. With udevadm hwdb a glob may take precedence over a hwdb entry even if the latter is sorted later. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
-
Peter Hutterer authored
Grey isn't pretty enough Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
And remove some of the unnecessary ones Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Not sure why this was in draw_tablet(), probably copy/paste Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 13, 2019
-
-
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
These numbers just happened to add up correctly for the motion history to produce a zero delta for a diagonal movement. Fix it by adding extra events to flush out any motion history leftovers. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This test had a loop around the proximity events, so in theory we could've sent two proximity-in events and still get a positive test. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Where we test for changes on tip state, we need the hover feature Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The totem, also a tablet tool, is a tool that is always tip-down and does not support hovering so we need to be able to distinguish this for tests. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The Dell Canvas Totem only has the MT axes but not the single touch ones. Make sure we copy the axis extents correctly. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-