1. 22 May, 2020 3 commits
    • Peter Hutterer's avatar
      tablet: handle a valid prox-out sequence after a forced proximity out · 0b221c6c
      Peter Hutterer authored
      With the previous patches a tablet would ignore a valid proximity out sequence
      where it happends after a forced prox-out. Fix this by checking the state when
      we're in forced proximity out - if we have a zero tool state but a tool
      updated then we did get a proximity out.
      
      And fix the existing test to check for that case.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      0b221c6c
    • Peter Hutterer's avatar
      Revert "tablet: don't disable the proximity quirk on good sequences" · c457050d
      Peter Hutterer authored
      This quirk was introduced for #248 was caused by buggy input-wacom drivers,
      not by actual firmware, see
      #381 (comment 279371)
      
      This appears to be the only tablet where this fix was needed, but we've been
      playing whack-a-mole ever since to work around the various other tablets that
      break with this behavior in place.
      
      So let's revert that fix and hope there aren't any other tablets out there
      (and if they are, we can probably quirk those). The revert makes the ISDV4 pen
      quirk obsolete (see 9cb089f2), so this was
      folded into this commit.
      
      This reverts commit 4f63345b.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      c457050d
    • Matt Mayfield's avatar
      touchpad: restore thumb detection while keeping fixes from !292 · 73870d93
      Matt Mayfield authored
      !292 improved libinput's ability to detect multiple-finger clicks when
      the fingers were not aligned close to horizontally. However that caused
      thumb detection to fail in several use cases.
      
      This patch restores thumb detection for
      - 2+ finger physical clickpad presses
      - resting thumb while two-finger scrolling
      - touches in the thumb exclusion area during multi-finger taps
      and improves pinch detection when thumb is centered below fingers.
      
      It also further enhances the flexibility of finger position for 2-, 3-,
      or 4-finger taps: if all tapping fingers land on the touchpad within a
      short time (currently 100ms), they will all count regardless of
      position (unless below the lower_thumb_line).
      Signed-off-by: Matt Mayfield's avatarMatt Mayfield <mdmayfield@yahoo.com>
      73870d93
  2. 21 May, 2020 2 commits
  3. 13 May, 2020 2 commits
    • Peter Hutterer's avatar
      evdev: warn if our event processing lags by 10ms or more · bd7b9106
      Peter Hutterer authored
      Take a snapshot of the time every 10 libinput_dispatch() calls. During event
      processing, check if the event timestamp is more than 10ms in the past and
      warn if it is. This should provide a warning to users when the compositor is
      too slow to processes events but events aren't coming in fast enough to
      trigger SYN_DROPPED.
      
      Because we check the device event time against the dispatch time we may get
      warnings for multiple devices on delayed processing. This is intended, it's
      good to know which devices were affected.
      
      In the test suite we need to ignore the warning though, since we compose the
      events in very specific ways it's common to exceed that threshold
      (particularly when calling litest_touch_move_to).
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      bd7b9106
    • Peter Hutterer's avatar
      test: fix the lookup for the timer offset warnings · 2ff0c342
      Peter Hutterer authored
      This was changed in 5e25bdfb but the litest
      message lookup wasn't changed. Let's do that now and change to a generic
      wording we can re-use for other messages.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      2ff0c342
  4. 12 May, 2020 1 commit
  5. 08 May, 2020 1 commit
  6. 19 Apr, 2020 4 commits
  7. 18 Apr, 2020 1 commit
  8. 16 Apr, 2020 2 commits
  9. 11 Apr, 2020 7 commits
  10. 06 Apr, 2020 1 commit
  11. 04 Apr, 2020 1 commit
  12. 31 Mar, 2020 1 commit
    • Peter Hutterer's avatar
      tablet: use the AttrPressureRange quirk for tablets too · 72af32c8
      Peter Hutterer authored
      The Aiptek 8000U has a pressure offset above our default (%5) but no
      meaningful way of detecting that. It doesn't provide distance or BTN_TOOL_PEN
      either, so our heuristics can't hook onto anything. BTN_TOUCH is set by this
      tablet but not at consistent pressure thresholds.
      
      Work around this by shipping a quirk that ups it to 70. Aiptek
      re-uses USB IDs because of course they do, so this applies to more than one
      device. Let's see what breaks.
      
      Fixes #462Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      72af32c8
  13. 30 Mar, 2020 5 commits
  14. 29 Mar, 2020 1 commit
  15. 25 Mar, 2020 2 commits
  16. 23 Mar, 2020 5 commits
  17. 22 Mar, 2020 1 commit