- May 26, 2021
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- May 25, 2021
-
-
Peter Hutterer authored
Always prefix the ninja args with the FDO_CI_CONCURRENT values (i.e. how many jobs the runner tells us). Note that this variable is currently not passed through to the qemu jobs, so inside the VM we'll still use the ninja default values. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- May 24, 2021
-
-
José Expósito authored
Remove fallthrough comments followed by a break statement. No functional changes. Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
Signed-off-by: weizhixiang <weizhixiang@uniontech.com>
-
Signed-off-by: weizhixiang <weizhixiang@uniontech.com>
-
- May 19, 2021
-
-
satrmb authored
Signed-off-by: satrmb <10471-satrmb@users.noreply.gitlab.freedesktop.org>
-
Windows allows "about a third of a second" to trigger a two-finger pinch. libinput/libinput#550 Signed-off-by: novenary <streetwalkermc@gmail.com>
-
When pinching, the thumb tends to move slower than the finger, so we may suppress it too early. Add a grace period during which it may be revived. Signed-off-by: novenary <streetwalkermc@gmail.com>
-
A pinch is defined as two fingers moving in different directions, and a scroll as two fingers moving in the same direction. Often enough when the user is trying to pinch, we may initially see both fingers moving in the same direction and decide that they want to scroll. Add a grace period during which we may transition to a pinch in those situations. Test fix: touchpad_trackpoint_buttons_2fg_scroll emits movements that change the distance between fingers, which triggers this new transition and makes the test fail; correct this. Signed-off-by: novenary <streetwalkermc@gmail.com>
-
Generated with a script to scrape the openrazer project for Razer Blade internal keyboard VIDs, see `razer_quirk_util.py` [1] This allows us to potentially bulk-add all Razer Blade models to benefit from palm rejection, rather than processing individual requests and merges. [1] https://gist.github.com/danryu/ee0c24ac50af40321550462bbf9ab594 Signed-off-by: dan g <dan.garton@gmail.com>
-
- May 18, 2021
-
-
Peter Hutterer authored
Let a few obvious modifiers through, including the F-key range. Especially left control is useful to know if it's down. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
The kernel emulates key events on its own anyway, replaying key events with libinput replay as well just duplicates the events. Turning kernel repeat off is not an option, it makes the device look different (EV_REP changes). So let's just not replay those events. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- May 12, 2021
-
-
Peter Hutterer authored
Use a scan-build wrapper to generate plist files, then parse those into a JUnit xml format. This makes the errors appear on the main MR page as opposed to being hidden in the artifacts somewhere. 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>
-
- May 05, 2021
-
-
Peter Hutterer authored
New commandline switch --with-hidraw. This will open all hidraw devices associated with this device and add any reports to the output in the form: events: - hid: time: [0, 0] hidraw1: [0x01, 0x02, 0x03, 0x05, 0x06] hidraw2: [0x07, 0x08, 0x09, 0x0a, 0x0b] - evdev: ... i.e. there's a nesting of `hid` with a list of reports, each with the hidraw node as dictionary entry. Because hidraw events do not have timestamps and always occur before the evdev events, they are in a separate frame (as shown above). We could try to figure out how to match them with the upcoming evdev frame but it's not worth it for now. The timestamp itself is a special key in the hidraw with the timestamp from clock_gettime. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- May 04, 2021
-
-
Nicolas Fella authored
CMake provides a nice way to use libinput, let the world now. Signed-off-by: Nicolas Fella <nicolas.fella@gmx.de>
-
Signed-off-by: Hans Gaiser <hansg91@gmail.com>
-
- Apr 30, 2021
-
-
Peter Hutterer authored
New output: hid: [ 0x05, 0x0d, 0x09, 0x04, 0xa1, 0x01, 0x85, 0x01, 0x09, 0x22, 0xa1, 0x02, 0x09, 0x42, 0x15, 0x00, 0x25, 0x01, 0x75, 0x01, 0x95, 0x01, 0x81, 0x02, 0x75, 0x01, 0x81, 0x03, 0x75, 0x06, 0x09, 0x51, 0x25, 0x3f, 0x81, 0x02, 0x26, 0xff, 0x00, 0x75, 0x08, 0x09, 0x48, 0x81, 0x02, 0x09, 0x49, 0x81, ... Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
YAML does support hex as long as it's 0x-prefixed. The comment here (probably) dates from an in-development version of libinput-record that used JSON. Anyway, let's print the HID report descriptor as hex because that's the common format for it. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We want to be able to print single-character strings. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 29, 2021
-
-
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>
-
- Apr 23, 2021
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 21, 2021
-
-
Peter Hutterer authored
This assumption dates back roughly a decade when INPUT_PROP_BUTTONPAD was introduced into the kernel. To my knowledge, devices right now erroneously advertise INPUT_PROP_BUTTONPAD when they are not a clickpad (but then they have BTN_RIGHT) or they lack INPUT_PROP_BUTTONPAD (and only have BTN_LEFT). So let's change our assumption here - if a clickpad has a right button log the kernel bug and continue with the assumption the device is a touchpad with physical buttons. To disable that warning, fix the kernel or add an AttrInputPropDisable quirk for the device. Fixes #595 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
There is only one touchpad with a physical left button but no right button and that is the old Apple touchpad, discontinued in 2008. Not a huge number of those left, I assume. So let's change our assumptions because these days the vast majority of touchpads are clickpads - any touchpad that only has a left button is treated as clickpad, even where the kernel doesn't set the INPUT_PROP_BUTTONPAD. We do need to check for BTN_LEFT as well though, because Wacom touchpads (i.e. the touch part of non-integrated Wacom tablets) don't have a left button either. 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>
-
- Apr 20, 2021
-
-
This touchpad is a pressure pad and needs the pressure handling disabled. Fixes #604 Signed-off-by: Udo Rader <udo.rader@bestsolution.at>
-
- Apr 14, 2021
-
-
Peter Hutterer authored
Fixes #599 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 13, 2021
-
-
Move the code in used to detect motion based gestures (scroll, swipe and pinch) to tp_gesture_detect_motion_gestures. Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
Move tp_gesture_same_directions, tp_gesture_mm_moved and tp_gesture_init_pinch to be able to use them in future commits. Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
Use a bool instead of an int and also rename the variable to avoid ambiguity with tp_filter_motion(). Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
Change the "cancel" parameter in the existing notify methods (swipe, pinch and gesture_notify) from int to bool. It is used as boolean, the fact that it's an int is just a historical quirkyness. Signed-off-by: José Expósito <jose.exposito89@gmail.com>
-
- Apr 09, 2021
-
-
Chris Dickson authored
Signed-off-by: Chris Dickson <hobochili@pm.me>
-
Peter Hutterer authored
This causes a bunch of "your system is too slow" messages in e.g. the various gesture tests. Fixes 95a72990 Fixes #601 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Apr 07, 2021
-
-
Peter Hutterer authored
The dispatch time is taken during libinput_dispatch(), i.e. at the beginning of an event sequence. We always read all events off the device, so where events come in while we're inside the main dispatch loop, our event time may be later than the saved dispatch_time. This causes an uint underflow and our tdelta > 10 will be true for that case. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-