1. 29 May, 2018 3 commits
  2. 21 May, 2018 4 commits
    • Chow Loong Jin's avatar
      Bump TRACKPOINT_DEFAULT_MAX_DELTA to 120 · 8e30b306
      Chow Loong Jin authored
      This raises the trackpoint speed limit to something more conducive to
      long-distance moves.
      https://bugs.freedesktop.org/show_bug.cgi?id=106506Signed-off-by: Chow Loong Jin's avatarChow Loong Jin <hyperair@debian.org>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      filter: improve touchpad acceleration · d6e53134
      Peter Hutterer authored
      This seems to give me roughly the same behaviour as macos does on the default
      0 speed setting.
      * Default speed is lower than before by around 30% [1]
      * Acceleration kicks in much sooner (130mm/s vs 250mm/s before)
      * Acceleration kicks in slower at lower speeds, so the change from 130mm/s to
        150mm/s is less than that of 320mm/s to 350mm/s
      * The effect of the speed setting is a wide-range constant (de|ac)celeration
        [2], which means:
        * The unaccelerated baseline up until the threshold now changes with the
          speed setting
        * The threshold is now the same for all speeds
        * The range of the speed setting should now easily cover all desired device
        * Acceleration is steeper at higher speeds
      * Deceleration was left as-is.
      [1] This may or may not fix the jumping pointer issues caused by the previous
      high defaults. When you have high default acceleration you move the finger
      slower. This slow movement caused some touchpads (mostly seen on Lenovos) to
      create pointer jumps. These weren't seen on synaptics previously because of a
      combination of higher user finger speed (thus not triggering the bug) or just
      not being as obvious (2px jump vs 10 px jump).
      [2] The speed setting is actually a curve, the closer you get to 1.0 the more
      difference you see between two different values. The curve's points are:
      -1/0, 0/1, 1/5, so the resolution is closer for slow speeds. We still have
      double resolution on the setting though so you'll find what you want.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      Revert "Expose a custom acceleration profile" · 33162632
      Peter Hutterer authored
      This looked good on paper but clearly no-one (including myself) ever tested this
      in a real-life situation or they would've noticed that the constant factor is
      missing, causing a segfault on the first two-finger scroll event, touchpad
      gesture or button scrolling.
      Adding the constant factor makes the API much worse and the benefit is
      unclear, so out of the window it goes. We can revisit this for libinput 1.12
      but this isn't going to make the next release.
      This reverts commit d8bd6505.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar
      Revert "touchpad: allow custom profiles on touchpads" · eae33ffc
      Peter Hutterer authored
      This reverts commit f6d61dc3.
  3. 18 May, 2018 2 commits
  4. 17 May, 2018 1 commit
  5. 16 May, 2018 2 commits
  6. 15 May, 2018 1 commit
  7. 14 May, 2018 1 commit
  8. 10 May, 2018 2 commits
    • Peter Hutterer's avatar
      Fix the scan-build fake leaks · f2069038
      Peter Hutterer authored
      We pass the event to libinput_post_event() where it is appended to the event
      queue. Except in these three cases clang doesn't seem to realize what's
      happening and complains about memory leaks. I tried workarounds like
      g_steal_pointer() but nothing I tried helps. So let's just pretend we're
      freeing it when clang looks at us.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • friedrich's avatar
      touchpad: fix tapping that happens after a moving thumb · af861523
      friedrich authored
      When finger movement exceeded the motion threshold before the finger was
      recognized as a thumb, it would never be regarded as a thumb by the tap system.
      This prohibited tapping until the thumb was lifted.
      This is fixed by moving the check for the thumb state up such that it
      happens before the motion threshold check.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  9. 03 May, 2018 8 commits
  10. 02 May, 2018 3 commits
  11. 30 Apr, 2018 2 commits
  12. 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,
      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>
  13. 26 Apr, 2018 6 commits
  14. 25 Apr, 2018 1 commit
  15. 20 Apr, 2018 1 commit
  16. 19 Apr, 2018 2 commits