- 24 Mar, 2015 1 commit
-
-
Peter Hutterer authored
Signed-off-by:Peter Hutterer <peter.hutterer@who-t.net>
-
- 23 Mar, 2015 1 commit
-
-
Peter Hutterer authored
Except for a few axes where this may be correct, a min == max axis range indicates a broken kernel driver. To avoid potential divisions by zero when scaling this axis later, reject such a device outright. Signed-off-by:
Hans de Goede <hdegoede@redhat.com>
-
- 20 Mar, 2015 1 commit
-
-
Peter Hutterer authored
This reverts commit 0e64837f. Rather than a customized touchpad property, let udev handle this and set the absinfo struct during the normal setup procedures. No need for libinput to have a custom workaround here. Signed-off-by:
-
- 19 Mar, 2015 5 commits
-
-
Peter Hutterer authored
Replaced by gdk_cursor_new_from_display() which means we need to tickle the event until it spits out a GdkDisplay. Deprecated in gdk 3.16 Signed-off-by:
-
Peter Hutterer authored
Make sure that if we go in one direction, then change flip over to the other direction we actually stop going into that direction, and the delta is lower than whatever the previous delta was (i.e. acceleration resets). Signed-off-by:
-
Peter Hutterer authored
If the delta is 0, the distance is the number of units (within this ms). Delta 1 means velocity across 2 ms, etc. Bonus: this doesn't return infinite speed anymore if we get more than one event per ms. This can happen on any device approaching 1000Hz poll rate, but definitely got triggered by the test suite. Actual effect was limited, since we cap out acceleration at max_accel we just hit this earlier and it stayed there. Signed-off-by:
-
Peter Hutterer authored
Delta movements on most slower movements are less than 1.0 per event, so we'd end up with an undefined direction for all of them. This led to the velocity being calculated across opposite movements rather than (as intended) across movements within a shared octant. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
- 18 Mar, 2015 2 commits
-
-
Peter Hutterer authored
This reverts commit d101d43d. This commit was accidentally merged, it was sitting on top of the wip branch. With the 0e64837f commit this isn't necessary anymore. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
- 17 Mar, 2015 11 commits
-
-
Peter Hutterer authored
A large range of the Apple touchpads seem to have the same dimensions. Use that fact to force-set a resolution. Signed-off-by:
-
Peter Hutterer authored
No functional changes Signed-off-by:
-
Peter Hutterer authored
Not all touchpad kernel drivers supply the x/y resolution. Let the udev hwdb fix this up where possible and read the value from it. This is intentionally only used on touchpads, touchscreen devices without resolution should be considered buggy and fixed in the kernel. Signed-off-by:
-
Peter Hutterer authored
Make the helper function accessible from other places (will be needed in an upcoming patchset). This also now takes a custom resolution as argument instead of always setting it to 1, and allows overriding a fake resolution after the fact. And instead of a hardcoded 1 everywhere, use a define for the resolution. Signed-off-by:
-
Peter Hutterer authored
This way the unaccelerated deltas returned by libinput are correct. To maintain the current behavior we slow down the input speed by the magic factor and likewise the accelerated output speed. This produces virtually the same accelerated deltas as the previous code. The magic factor is applied to the default denominator for guessing a resolution based on the touchpad diagonal. We can't really get around this without having a resolution from the touchpad; meanwhile this produces virtually the same coordinates before/after. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
We really don't need to deal with devices that have x but not y or vice versa. Signed-off-by:
-
Peter Hutterer authored
These devices don't provide ABS_X/Y, but do have proper multitouch. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
The struct evdev_device's absinfo_x/y point to the right axis Signed-off-by:
-
Peter Hutterer authored
Unneeded, but better for symmetry. Signed-off-by:
-
- 16 Mar, 2015 12 commits
-
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Make it clear where we're dealing with device coordinates and where we're dealing with DPI-normalized coordinates. Signed-off-by:
-
Peter Hutterer authored
No functional changes. Signed-off-by:
-
Peter Hutterer authored
Everywhere else in the touchpad code we use "t" for the struct tp_touch. Signed-off-by:
-
- 15 Mar, 2015 6 commits
-
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
The helper function now prints an error message if the event type passed is not allowed. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
Peter Hutterer authored
We don't actually use TOUCH_CANCEL in libinput, but either way calling the slot on a cancel should be valid. Calling it on a FRAME event is not. Signed-off-by:
-
Peter Hutterer authored
Signed-off-by:
-
- 13 Mar, 2015 1 commit
-
-
Hans de Goede authored
The current default start location for the 2fg scroll tests: 47%, 50% and 53%, 50% are further than 3cm apart on the wacom-intuos-finger test device, causing test failures when pinch gesture support gets added. This fixes this, and also switches the fingers in the touchpad_2fg_scroll_slow_distance and touchpad_trackpoint_buttons_2fg_scroll tests to the default locations rather than putting them pretty far apart. Signed-off-by:
-
