1. 03 Aug, 2015 2 commits
  2. 30 Jul, 2015 2 commits
  3. 28 Jul, 2015 1 commit
  4. 22 Jul, 2015 1 commit
  5. 21 Jul, 2015 2 commits
  6. 15 Jul, 2015 1 commit
  7. 13 Jul, 2015 1 commit
  8. 09 Jul, 2015 1 commit
    • Peter Hutterer's avatar
      touchpad: add pressure-based thumb-detection · 3dcf28b9
      Peter Hutterer authored
      All touchpad recordings seen so far show that a value above 100 is definitely
      a thumb or a palm. Values below are harder to discern, and the same isn't true
      for touchpads supporting ABS_PRESSURE instead of ABS_MT_PRESSURE.
      The handling of a touch is as outlined in tp_thumb_detect:
      * thumbs are ignored for pointer motion
      * thumbs cancel gestures
      * thumbs are ignored for clickfinger count
      * edge scrolling doesn't care either way
      * software buttons don't care either way
      * tap: only if thumb on begin
      The handling of thumbs while tapping is the simplest approach only, more to
      come in follow-up patches.
      Note that "thumb" is the synonym for "this touch is too big to be a
      fingertip". Which means that a light thumb touch will still be counted as a
      finger. The side-effect here is that thumbs resting a the bottom edge of the
      touchpad will almost certainly not trigger the pressure threshold because
      most of the thumb is off the touchpad.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
  9. 06 Jul, 2015 5 commits
  10. 02 Jul, 2015 1 commit
    • Peter Hutterer's avatar
      Drop motion normalization of unaccelerated deltas · c06d825c
      Peter Hutterer authored
      This simply doesn't work for low-dpi mice. Normalizing a 400dpi mouse to a
      1000dpi mouse forces a minimum movement of 2.5 units and the resulting pixel
      jumps. It is impossible for the caller to detect whether the jump was caused
      by a single motion or multiple motion events.
      This is technically an API break, but not really.
      The accelerated data was already relatively meaningless, even if normalized as
      the data did not correspond predictably to any input motion (unless you know
      the implementation acceleration function in the caller). So we can drop the
      mention from there without expecting any ill effects in the caller.
      The unaccelerated data was useless for low-dpi mice and could only be used to
      measure the physical distance of the mouse movement - something not used in
      any caller we're aware of (if needed, we can add that functionality as a
      separate call). Dropping motion normalization for unaccelerated deltas also
      restores true dpi capabilities to users of that API, mostly games that want to
      make use of high-dpi mice.
      This is a simplified patch, the normalization is still in place for most of
      libinput, it merely carries the original coordinates in the event itself.
      In the case of touchpads, the coordinates are unnormalized into the x-axis
      coordinate space as per the documentation.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
  11. 16 Jun, 2015 1 commit
  12. 27 Apr, 2015 1 commit
  13. 21 Apr, 2015 1 commit
  14. 09 Apr, 2015 1 commit
  15. 25 Mar, 2015 2 commits
  16. 16 Mar, 2015 3 commits
  17. 23 Feb, 2015 4 commits