1. 28 Aug, 2018 1 commit
    • Peter Hutterer's avatar
      test: drop the sleep_ms argument · 7768d7d9
      Peter Hutterer authored
      This forces events for every ~10ms now. If we want a slower movement, we need
      more steps - just like a real touchpad does it.
      Cocinelle spatch files were variants of:
      	expression A, B, C, D, E, F, G, H, I, J, K;
      	- litest_touch_move_two_touches(A, B, C, D, E, F, G, H, I)
      	+ litest_touch_move_two_touches(A, B, C, D, E, F, G, H)
      The only test that needed a real fix was touchpad_no_palm_detect_2fg_scroll,
      it used 12ms before, now it's using 10ms so on the bcm5974 touchpad the second
      finger was a speed-thumb. Increasing the events and thus slowing down the
      pointer means it's a normal finger and the test succeeds again.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  2. 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>
  3. 23 Mar, 2018 1 commit
  4. 19 Nov, 2017 1 commit
  5. 20 Feb, 2017 1 commit
  6. 15 Jan, 2017 1 commit
  7. 12 Sep, 2016 1 commit
  8. 06 Sep, 2016 1 commit
  9. 02 Aug, 2016 1 commit
  10. 03 May, 2016 1 commit
  11. 31 Mar, 2016 1 commit
  12. 16 Jun, 2015 1 commit
  13. 01 Jun, 2015 1 commit
  14. 21 May, 2015 1 commit
  15. 01 May, 2015 1 commit
  16. 24 Dec, 2014 1 commit
    • Peter Hutterer's avatar
      Add pointer axis sources to the API · 20ac4b3a
      Peter Hutterer authored
      For a caller to implement/provide kinetic scrolling ("inertial scrolling",
      "fling scrolling"), it needs to know how the scrolling motion was implemented,
      and what to expect in the future. Add this information to the pointer axis
      The three scroll sources we have are:
      * wheels: scrolling is in discreet steps, you don't know when it ends, the
        wheel will just stop sending events
      * fingers: scrolling is continuous coordinate space, we know when it stops and
        we can tell the caller
      * continuous: scrolling is in continuous coordinate space but we may or may not
        know when it stops. if scroll lock is used, the device may never technically
        get out of scroll mode even if it doesn't send events at any given moment
        Use case: trackpoint/trackball scroll emulation on button press
      The stop event is now codified in the API documentation, so callers can use
      that for kinetic scrolling. libinput does not implement kinetic scrolling
      Not covered by this patch:
      * The wheel event is currently defined as "typical mouse wheel step", this is
        different to Qt where the step value is 1/8 of a degree. Some better
        definition here may help.
      * It is unclear how an absolute device would map into relative motion if the
        device itself is not controlling absolute motion.
      * For diagonal scrolling, the vertical/horizontal terminator events would come
        in separately. The caller would have to deal with that somehow.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Original patch, before the rebase onto today's master:
      Reviewed-by: 's avatarHans de Goede <hdegoede@redhat.com>
  17. 24 Nov, 2014 1 commit
  18. 11 Nov, 2014 3 commits
  19. 22 Sep, 2014 1 commit