- Jan 30, 2015
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 29, 2015
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
The laptops on this series have the physical trackpoint buttons back but wired them up to the touchpad instead of the trackpoint device and they appear as BTN_0, BTN_1 and BTN_2 for left, right, middle. The udev hwdb marks these for us with the TOUCHPAD_HAS_TRACKPOINT_BUTTONS tag [1]. Use that tag to identify them and re-route the events through the trackstick device after mangling the event codes to represent the actual buttons. [1] http://cgit.freedesktop.org/systemd/systemd/tree/hwdb/70-touchpad.hwdb Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Notable: sends BTN_0/1/2 instead of the trackpoint This device currently has the INPUT_PROP_TOPBUTTONPAD property set, kernel patches [1] and [2] are pending to remove this. This test device already lacks the property. [1] https://patchwork.kernel.org/patch/5730371/ [2] https://patchwork.kernel.org/patch/5730451/ Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Jan 28, 2015
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Jan 27, 2015
-
-
libinput complained with lots of "client bug" messages because the GUI tool did not check which axis values were available. Signed-off-by:
Friedrich Schöller <code@schoeller.se> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Vertical axis values were used for the horizontal axis as well. Introduced 1baf109b Signed-off-by:
Friedrich Schöller <code@schoeller.se> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 22, 2015
-
-
After switching my main workstation over to using xf86-input-libinput, I noticed that the multi-media keys like play/pause on my keyboard no longer worked. It turns out that the second hid interface on my keyboard which has the multimedia-keys, also declares having: BTN_BASE6 and BTN_MODE which both fell into the range we were using to test for something being a joystick. The commit makes our joystick test mode strict, restoring functionality of the multi-media keys on the keyboard in question. Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
This function was removed in 1baf109b Signed-off-by:
Marek Chalupa <mchqwerty@gmail.com> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 20, 2015
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 16, 2015
-
-
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> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Allow switching between softbuttons and clickfinger on any mt-capable clickpad. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> [hdegoede@redhat.com] Keep top softbuttons working when enabling clickfinger [hdegoede@redhat.com] Simply touchpad click method switching Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
- Jan 15, 2015
-
-
Peter Hutterer authored
Two methods are provided: * button area - used on most clickpads, a click with a touch within a given area generates left/middle/right clicks * clickfinger - used on apple touchpads, a click with 1/2/3 fingers on the touchpad generates a left, right, middle click Both methods already exist in the touchpad code, this is just the configuration interface. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Allow the center of pinned fingers to drift over time, to avoid accidentally unpinning fingers. BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=86807 Signed-off-by:
Hans de Goede <hdegoede@redhat.com> Reviewed-by:
Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Release one touch point at the same time as a fake touch. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
This device sends touch information before BTN_TOUCH https://bugs.freedesktop.org/show_bug.cgi?id=87197 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
An upcoming synaptics semi-mt device needs the same code. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Some touchpads provide touch information while the finger hovers over the touchpad, i.e. before BTN_TOUCH. Add a touch state for those touchpads so we can ignore the touches until they actually start. The approach is now: instead of BEGIN we mark a new touch as HOVERING. Use the BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP information during tp_process_state() to mark any touches that are hovering as down or ended. i.e. provided BTN_TOUCH is down: if BTN_TOOL_FINGER is down, one hovering touch gets marked as down, if DOUBLETAP is down, two touches are marked as down, etc. When ending touches, switch them back into HOVERING if the BTN_TOOL_FINGER is still set, otherwise end them properly. https://bugs.freedesktop.org/show_bug.cgi?id=87197 Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
BTN_TOOL_FINGER, DOUBLETAP, etc. are mutually exclusive in the kernel, so we can use ffs here instead of manually counting. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
We need this for determining hovering touches on some semi-mt touchpads. This makes the fake_touches mask use bit 0 for BTN_TOUCH, and the other bits for BTN_TOOL_FINGER, BTN_TOOL_DOUBLETAP, etc. BTN_TOUCH is independent of the rest, the others are mutually exclusive in the kernel. Since the mask isn't a straightforward bitmask anymore, abstract it all through helper functions. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Note: soname bump Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
We specify a bunch of other (static) things in the .in file, let's be consistent. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Fixes doxygen build with custom builddirs Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Some devices require more than just flipping around the buttons, such as tablets. When it comes to devices like tablets, because the position of the palm rest is on the right, the entire tablet has to be flipped around in order to be usable by lefties. As such, this requires that we reverse the coordinates of the tablets in addition to flipping the buttons on the tablet. As such, renaming these functions so that they aren't specific to devices where only the buttons are flipped seems appropriate. Signed-off-by:
Stephen Chandler Paul <thatslyude@gmail.com> Reviewed-by:
Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This is merged on top of the wheel normalization patches. Those introduced an axis source and an extra "discrete" value to the various internal and external APIs. This branch changed from a single value to passing dx/dy into all scroll events. The conflicts are to change everything to take x, y, x_discrete, y_discrete as values (and the source axis mask of course). Conflicts: src/evdev-mt-touchpad-edge-scroll.c src/evdev.c src/libinput-private.h src/libinput.c
-
- Jan 14, 2015
-
-
Peter Hutterer authored
The recent normalization of wheel events means we get the angle in degrees but we don't know how this corresponds to clicks. The M325 has a 20 degree click angle, most other mice have 15 degrees. So an angle of 60 can be 3 or 4 click events. Most clients care more about the click count than the angle on a mouse wheel. Provide that value when needed. Adding a discrete value to the axis event leaves the possibility of defining discrete units for finger/continuous scroll sources in the future. Right now, these will always reuturn 0. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jonas Ådahl <jadahl@gmail.com> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
- Jan 13, 2015
-
-
Peter Hutterer authored
Sending separate axis events instead of one unified events is limiting, especially when simultaneously scrolling in both directions and the caller tries to implement kinetic scrolling. Take a page from the tablet-support branch and instead implement the axis event as a generic event that can contain multiple axes simultaneously. Right now we only have two (scroll) axes and we could easily just check both for non-zero values. If we want to allow further axes in the future, we need a check whether an axis is set in an event, that's what libinput_event_pointer_has_axis to scroll events() is for. We also need the mask to notify of a scroll stop event, which could otherwise be confused as a vertical-only or horizontal-only event. This is an API and ABI break. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jonas Ådahl <jadahl@gmail.com>
-
Peter Hutterer authored
Similar to the mouse resolution, let's make the scroll distance a sensible predictable value. Most mice use a 15 degree angle per scroll click, so let's change to that. This will alter behaviour in clients that expect 10. We return doubles for the axis value, so that leaves the option of really fine-grained step sizes in the future. We currently assume all mice have 15 degree angles. Like the DPI settings, it will require a udev property to be set. Patch for that to follow. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jonas Ådahl <jadahl@gmail.com>
-
Peter Hutterer authored
prop isn't the full property line, just the value. And document the return value too while we're at it. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 11, 2015
-
-
Main has unused parameters argc and argv. Since they are unused and C 99 allows to prototype main as 'int main(void)', remove them and replace by void. It fixes build when unused parameters are treated as errors. Signed-off-by:
Marek Chalupa <mchqwerty@gmail.com> Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
- Jan 08, 2015
-
-
Peter Hutterer authored
Under gdb, signalfd will still deliver the signal when gdb itself is interrupted and quit event-debug. For a debugging tool, that's not optimal. Switch to a normal signal handler instead, signalfd is overkill here anyway. Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by:
Jonas Ådahl <jadahl@gmail.com>
-
- Jan 07, 2015
-
-
Peter Hutterer authored
Signed-off-by:
Peter Hutterer <peter.hutterer@who-t.net>
-
Jonas Ådahl authored
Signed-off-by:
Jonas Ådahl <jadahl@gmail.com> Reviewed-by:
Peter Hutterer <peter.hutterer@who-t.net>
-