- Mar 22, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
And fix up the one buggy call we had Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
https://bugs.freedesktop.org/show_bug.cgi?id=100122 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Print the axis values on proximity out because it a) ensures we have the right values and b) makes the output better aligned with the proximity in, so it's easier to spot in a log file. But don't print the tool capabilities because they're unrelated to the prox out anyway and again it makes the output easier to spot. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 14, 2017
-
-
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 effect since we don't care about the mouse itself. But when running on kernels without uinput's UI_GET_SYSNAME this can cause misdetection of the uinput device and test case failures. Simply picking a differently named device avoids that. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 09, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
If not set, libtool will search directories up to ../.. for an install-sh and then dump the aux files there. This caused a couple of problems with the xorg release.sh script that now uses worktrees but is generally bad behaviour because we can't guarantee that we're not inside some other repository. Set AC_CONFIG_AUX_DIR to avoid this behavior. See https://lists.freedesktop.org/archives/xorg-devel/2017-March/053006.html Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Emil Velikov <emil.velikov@collabora.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 08, 2017
-
-
Peter Hutterer authored
This device only sends ABS_PRESSURE https://bugs.freedesktop.org/show_bug.cgi?id=100106 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Mar 07, 2017
-
-
Peter Hutterer authored
https://bugs.freedesktop.org/show_bug.cgi?id=99975 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Mar 01, 2017
-
-
Peter Hutterer authored
If a touch started hovering in the main area, the button state would start with AREA and never move to the real button state, despite the finger triggering the pressure thresholds correctly in one of the areas. This could even happen across touch sequences if a touch went below pressure in the software button area, it changed to hovering and the button state changed to NONE. On the next event, the touch is still hovering and the current position of the touch is taken for the button state machine. https://bugs.freedesktop.org/show_bug.cgi?id=99976 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 28, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Introduced in commit 8e7f99c2 we only allowed horizontal edge scrolling on devices larger than 50mm to leave enough reactive space on the touchpad. Looking at a ruler, a 50mm high touchpad is still large enough to leave the bottom 7mm as an horizontal edge scroll area. Reduce the minimum size to 40mm instead, that's closer to where it starts to get a bit iffy. https://bugzilla.redhat.com/show_bug.cgi?id=1422221 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 27, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
-
- Feb 26, 2017
-
-
Peter Hutterer authored
We don't cater for the special case of groups having a different number of modes, there is no hardware right now that does that. 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>
-
- Feb 24, 2017
-
-
Peter Hutterer authored
Supresses any printf statements from the tool itself, i.e. it skips printing any of the events. Makes it easier to debug the internal state since it's not intermixed with a whole lot of messages about the events that are generated. Best combined with --verbose (yes, hilarious, isn't it...) Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Prefix device log messages with the device's sysname so it's more obvious where the messages are coming from. This makes it much easier to grep for a specific device's messages but also adds some identifier to messages that were previously without any identifier (e.g. all the state machine debugging) All info and error messages also automatically prefix the device name, so those messages are standardised too, e.g an info message now: event4 - SynPS/2 Synaptics TouchPad: is tagged by udev as: Touchpad a debug message now: event4 - using pressure-based touch detection And since this required changing a lot of the strings in messages anyway, polish a few minor things too. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Preparation work for standardizing log messages better Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Acked-by: Hans de Goede <hdegoede@redhat.com>
-
- Feb 23, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 22, 2017
-
-
Peter Hutterer authored
Easier to track if we leave the original files alone. Actual changes to the doxygen style: * indent <dd> blocks * hide the navigation sub-items. Our current style expands the full navigation menu but File-list, etc. is mostly useless and just wastes space. * force some space below the main bar * change the header sizes around a bit. Primary goal here: making <h1> smaller than the title 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
It was just floating around lonely there and I doubt anyone really used 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
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 21, 2017
-
-
Peter Hutterer authored
-
Peter Hutterer authored
The range that matters is 0-200, maybe up to 400 if you account for really fast movements. But to match other, published, accel curves default to up to 1000 mm/s. It's easy enough in gnuplot to reduce the range. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
Missing from 8c1aa1de where we hid the human-readable parts but the keycode itself is still enough information to recover the typed bits. Print it as -1 as that keycode doesn't exist for real keys so it stands out nicely. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
- Feb 20, 2017
-
-
Peter Hutterer authored
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
-
Peter Hutterer authored
This may be a feature for the future but for now be honest and don't claim that button-based scrolling is available, it's not hooked up in the absolute code path. https://bugs.freedesktop.org/show_bug.cgi?id=99865 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
Before, our states were idle, button down and scrolling. This adds a state where the button is down and the timeout has expired (i.e. we're ready to send scroll events) but we haven't actually sent any events anymore. If the button is released in this state, we generate a normal click event. https://bugs.freedesktop.org/show_bug.cgi?id=99666 Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-
Peter Hutterer authored
No functional changes, preparation work for adding another state. 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
This is merely 'button scrolling' now, only the original implementation was middle button only. And to avoid confusing with the middle button emulation, drop "MIDDLE" from the define. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> Reviewed-by: Hans de Goede <hdegoede@redhat.com>
-