- Aug 08, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Pens that don't have a pressure offset (caused by a worn-out tip) still have basic pressure thresholds to avoid tip events when we're still a bit away from the tablet or barely touching it. That range is currently 5% of the pressure for tip down, 1% for tip up. This leaves us with 95% of the range and that needs to be scaled correctly, otherwise the bottom 5% happen before a tip event and are inaccessible where applications don't look at pressure before tip down. Fixes #332 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Theoretically this shouldn't matter, but testing at the far end of the range is bound to trigger some little issues eventually that should be triggered explicitly, not by accident. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Previously, the pressure range was calculated from the axis total range. A device with a pressure offset making the bottom 10% inaccessible would lose 10% of that range as non-accessible. Due to the implementation, this affected the upper range of the device, so the top N percent became unaccessible. Which may be why no-one's noticed this yet. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The offset handling was inconsistent, stored as relative to the axis minimum but used as absolute in some places. Fix this by always using the absolute value including the minimum (i.e. no pressure offset means offset == minimum). Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Unsuprisingly, a normalized [0,1] value will always be between 0 and 1, so bhis gave us a false positive. Check for the real values instead. Those values aren't 100% correct because of a bug in the offset handling which will be fixed in a follow-up commit. The difference is near enough that it doesn't matter here 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
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Aug 07, 2019
-
-
Benjamin Tissoires authored
On a very loaded machine, the process might not receive the quit signal in a timely manner, and this introduce false positive results. Add a longer timeout. This shouldn't interfere with the global time spent in the tests, but will allow some loaded environment to pass the tests. Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Benjamin Tissoires authored
See freedesktop/freedesktop#178 (comment 203050) Some shared runners are not capable of understanding OCI format for container images, and they are failing. Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Benjamin Tissoires authored
This parameter is already included by default in ci-templates, but we also need it in freebsd Signed-off-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
-
Peter Hutterer authored
This way it can't leak into the meson testlog.txt during the other stages. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Gitlab supports masked tokens that get sanitized during log output but these tokens are still in the environment. meson dumps the environment into testlog.txt, resulting in our tokens leaking. Avoid that leak by using a netrc file instead. The token value now refers to the file name which is safe enough to leak into the test logs. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Aug 04, 2019
-
-
In evdev_device_calibrate, the user matrix was not being stored when it was the identity matrix. This resulted in libinput_device_config_calibration_get_matrix not providing the correct matrix. Instead of giving the identity matrix, the last non-identity matrix set was given. This just moves the storage of the user matrix in evdev_device_calibrate to be above the identity matrix early return so that it always get stored. Signed-off-by: Brian Ashworth <bosrsf04@gmail.com> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Aug 02, 2019
-
-
Peter Hutterer authored
meson implicitly sets install to whether install_dir is nonzero. Which means it's superfluous anyway and removing it drops the meson warning: WARNING: Project specifies a minimum meson_version '>= 0.41.0' but uses features which were added in newer versions: * 0.50.0: {'install arg in configure_file'} Fixes #334 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jul 31, 2019
-
-
Peter Hutterer authored
Found by coverity. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If we don't supply --with-libinput, the device is NULL so we can't unref it. 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
We keep running into the proximity timeout for these tests, especially under valgrind. To avoid this, manually intersperse the touch events with tablet events. Note that this manual loop would just work even without tablet events because we no longer have a 10ms delay between touch events as enforced by litest_touch_move_to. But let's do the right thing anyway. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jul 29, 2019
-
-
In order for two devices to be in the same group, they need to share identical LIBINPUT_DEVICE_GROUP attributes. The `wacom_handle_ekr` function overwrites the VID/PID for an ExpressKey Remote, but the 'phys' path is left unchanged. This only works if the EKR and the device we want to pair it with are both direct sibings in the USB tree. It isn't always possible to actually connect the devices like this, however. The Cintiq Pro 32 and 24, for instance, have multiple internal USB hubs and place the pen sensor and the USB port for the EKR dongle behind different ones. By copying the 'phys' path of the device we want to pair with, it is possible to reproduce the entire LIBINPUT_DEVICE_GROUP and ensure that the two devices actually end up paired in libinput. Signed-off-by: Jason Gerecke <jason.gerecke@wacom.com>
-
- Jul 28, 2019
-
-
Jacob Moroni authored
It is required, otherwise the trackpoint is too sensitive. Tested with a Dell Latitude 5580. Signed-off-by: Jacob Moroni <mail@jakemoroni.com>
-
- Jul 24, 2019
-
-
Peter Hutterer authored
Fixes #324 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
When verifying a recording, let's skip those tests that require events but don't have any. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jul 19, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jul 17, 2019
-
-
Peter Hutterer authored
-
- Jul 16, 2019
-
-
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Instead of a simple yes/no/maybe for thumbs, have a more extensive state machine that keeps track of the thumb. Since we only support one thumb anyway, the tracking moves to the tp_dispatch struct. Test case changes: touchpad_clickfinger_3fg_tool_position: with better thumb detection we can now handle this properly and expect a right button (2fg) press for the test case touchpad_thumb_no_doublethumb_with_timeout: two thumbs are now always two fingers, so let's switch to axis events here Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Jul 15, 2019
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
-
Peter Hutterer authored
We don't need speed detection for non-clickpads - the only reason to ever drop a second finger on those is to either scroll or trigger a gesture. Unlike clickpads, where a dropped finger may be a thumb to click. 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
Only sets the state to YES at the moment, will do more in the future. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Check if there's a thumb if we have two touches. If one finger moves but the thumb remains still, we assume that one is really a thumb. But if the thumb moves while the finger is still, let's assume this is a 2-finger scroll. Extracted from Matt Mayfield's thumb detection patchset
-
Peter Hutterer authored
We can't detect pinch when gestures are off anyway, so we don't need to check the finger distances. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Only bias towards scrolling if the fingers are in the position past the timeout.
-
Put some basic location checks in, if the fingers are next to each other and vertically close, assume scroll over swipe. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>:>
-