- 29 Apr, 2021 1 commit
-
-
Peter Hutterer authored
To update your local repository, use these commands $ git fetch origin $ git checkout master $ git branch -m main $ git branch --set-upstream-to=origin/main Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 23 Apr, 2021 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 21 Apr, 2021 4 commits
-
-
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>
-
- 20 Apr, 2021 1 commit
-
-
This touchpad is a pressure pad and needs the pressure handling disabled. Fixes #604 Signed-off-by:
Udo Rader <udo.rader@bestsolution.at>
-
- 14 Apr, 2021 1 commit
-
-
Peter Hutterer authored
Fixes #599 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 13 Apr, 2021 5 commits
-
-
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>
-
- 09 Apr, 2021 2 commits
-
-
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>
-
- 07 Apr, 2021 1 commit
-
-
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>
-
- 06 Apr, 2021 2 commits
-
-
Jonas Ådahl authored
We don't want the file to be left open after any fork/exec, and we don't want the read to be blocking; so open it as such. Signed-off-by:
Jonas Ådahl <jadahl@gmail.com>
-
Don't middle click on clickpads with click method clickfinger when more than 3 fingers are used. Signed-off-by:
José Expósito <jose.exposito89@gmail.com>
-
- 03 Apr, 2021 1 commit
-
-
Ben authored
Signed-off-by:
Ben Weston <b.weston60@gmail.com>
-
- 29 Mar, 2021 9 commits
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
For historical (but not very good) reasons, libinput record printed events from the first device to the output file (or stdout) and buffered everything else. On ctrl+c, the other devices' descriptions and the buffered events were appended to the output file. This makes the printing code rather complex. Simplify it by giving each device a separate FILE* - the first device points to the real output file, the others to a tempfile. On Ctrl+C we just append those tempfiles to the real output file one-by-one and done. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Less confusing than having output_file, out_file, and outfile. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
No functional changes since we can get this easily from the list itself, but in the future the first device will be used more extensively. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Using list_insert() here means the last device specified on the commandline is the one that ends up in the file first - not very obvious... Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Our file format is static enough that we don't need to use push/pop, we know exactly which line is going where. So let's replace it with a static indent instead. 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
This is prep work to be more consistent with the use of tempfile later for individual devices. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
With a new helper function strv_from_argv we can re-use the device opening loop for all the use-cases we have. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 26 Mar, 2021 4 commits
-
-
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>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- 19 Mar, 2021 1 commit
-
-
José Expósito authored
EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs: https://editorconfig.org/ Signed-off-by:
José Expósito <jose.exposito89@gmail.com>
-
- 17 Mar, 2021 6 commits
-
-
Signed-off-by:
José Expósito <jose.exposito89@gmail.com>
-
The current fallback_dispatch wheel struct, a device_coords, doesn't allow to save extra information. The new anonymous struct will allow to add a is_inhibited field to disable mouse scroll while the middle button is pressed and, potentially, any required extra state in the future. Signed-off-by:
José Expósito <jose.exposito89@gmail.com>
-
The FreeBSD HID stack adds the device type to the evdev name, so we get e.g. "ACPI0C50:00 18D1:5028 TouchPad". (Maybe this shouldn't be matched by name at all though...) Signed-off-by:
Greg V <greg@unrelenting.technology>
-
FreeBSD does not use Linux modaliases, so we have to generate these strings. Unfortunately for us, the data in kenv has the chassis type pre-parsed into a nice string, so we have to match these strings back into numbers. Only relevant types are included to avoid bloating the code. Signed-off-by:
Greg V <greg@unrelenting.technology>
-
The Linux applespi driver currently uses the Synaptics vendor ID on the trackpad for some reason (even though, at least from bcm5974 we only know that Broadcom is involved..) but my upcoming FreeBSD driver uses the Apple vendor ID everywhere, so add two quirks. Signed-off-by:
Greg V <greg@unrelenting.technology>
-
Apple MacBooks (Broadwell/Skylake/Kaby Lake and Apple Silicon) use SPI to communicate with the keyboard and trackpad. Signed-off-by:
Greg V <greg@unrelenting.technology>
-
- 16 Mar, 2021 1 commit
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-