1. 29 Aug, 2018 1 commit
  2. 22 Aug, 2018 1 commit
    • Kim Lindberger's avatar
      Add quirk to control velocity averaging, disable it by default · 99334e11
      Kim Lindberger authored
      libinput applies averaging to the velocity of most pointer devices. Averaging
      the velocity makes the motion look smooth and may be of benefit to bad input
      devices. For good devices, however, it comes at the unfortunate price of
      decreased accuaracy.
      
      This change turns velocity averaging off by default (sets ntrackers to 2 instead
      of 16) and allows for it to be turned back on via a quirk, for bad devices which
      require it.
      99334e11
  3. 20 Aug, 2018 1 commit
    • Peter Hutterer's avatar
      touchpad: improve pointer jump detection · eca2f8c9
      Peter Hutterer authored
      Previously, we had a hard threshold of 20mm per event frame. That is just
      about achievable by really fast movements (in which case you don't care too
      much about the jumps anyway because you've already hit the edge of the screen).
      
      Sometimes pointer jumps have lower deltas that are achievable even on slower,
      more likely motions. Analysis of finger motion has shown that while a delta
      >7mm per event is possible, jumping _by_ 7mm between two events is unlikely
      and indicates a pointer jump. So let's diff the most recent delta and the
      current delta, if it increases by 7mm between two event frames let's say it's
      a pointer jump and discard it.
      
      Helps with but does not fully resolve:
      #80
      #36
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      eca2f8c9
  4. 10 Aug, 2018 1 commit
  5. 03 Aug, 2018 1 commit
  6. 19 Jul, 2018 1 commit
    • Peter Hutterer's avatar
      touchpad: don't NONE or HOVERING touches towards the touch · 23d5f2a5
      Peter Hutterer authored
      To trigger this, we'd need 1, 2, 3 fingers down, release fingers 1 and 2 but
      keep 3 down. Then put finger 1 down again. Touches 1 and 3 are alive now,
      touch 2 is in state NONE.
      
      During the thumb detection we took the first touch not in BEGIN and assigned
      it to "first" - this would now be the second touch in state NONE.
      
      Real effect is relatively minimal since we only use the coordinates here.
      
      Fixes #89
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      23d5f2a5
  7. 29 Jun, 2018 1 commit
  8. 26 Jun, 2018 1 commit
  9. 15 Jun, 2018 1 commit
  10. 13 Jun, 2018 1 commit
  11. 11 Jun, 2018 1 commit
  12. 08 Jun, 2018 1 commit
  13. 29 May, 2018 2 commits
  14. 21 May, 2018 1 commit
  15. 18 May, 2018 2 commits
  16. 15 May, 2018 1 commit
  17. 03 May, 2018 3 commits
  18. 02 May, 2018 3 commits
  19. 27 Apr, 2018 1 commit
    • Peter Hutterer's avatar
      touchpad: fix the trackpoint event counter for the T460s · c0fd857d
      Peter Hutterer authored
      Introduced in 416fa44d
      
       but there was a logic
      error: we claimed to require 3 events from a trackpoint before stopping the
      touchpad but the timer was only set when we actually stopped the touchpad. So
      if a trackpoint sends a single event every second, we'd disable the touchpad
      after 3 seconds for the duration of the timeout, then again 3 seconds later,
      etc.
      
      Fix this by always setting the timeout and resetting the event counter if no
      activity happened.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      c0fd857d
  20. 26 Apr, 2018 1 commit
  21. 16 Apr, 2018 1 commit
  22. 05 Apr, 2018 2 commits
  23. 21 Mar, 2018 1 commit
    • Peter Hutterer's avatar
      touchpad: only keep low-pressure fingers alive for 2+-slot touchpads · 3f5ff113
      Peter Hutterer authored
      Regression introduced by 3979b9e1, bug 105258.
      With that commit, we only ended real touches when we had less than nslots fake
      fingers down. i.e. tripletap on a 2 slot touchpad would not end the
      first/second touch even if the pressure goes below the threshold. e.g. Lenovo
      x270 needs this, see https://bugs.freedesktop.org/attachment.cgi?id=137672, it
      dips below the pressure threshold for the first slot and ends the second slot
      in the same frame as the third finger is detected. Fun times.
      
      Anyway, this breaks semi-mt touchpads, another fine category of devices,
      because some of those can detect hovering fingers at low pressure, see bug
      105535. Because semi-mt devices are generally garbage, we treat them as
      single-touch devices instead. So whenever two fingers are down, we treat both
      as above the pressure threshold, even when they're physicall hovering.
      
      Fix this by making the x270 fix conditional on at least 2 slots.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=105535
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      3f5ff113
  24. 13 Mar, 2018 2 commits
  25. 12 Mar, 2018 1 commit
  26. 08 Mar, 2018 2 commits
  27. 05 Mar, 2018 3 commits
  28. 01 Mar, 2018 2 commits