1. 21 Jan, 2019 5 commits
  2. 07 Jan, 2019 6 commits
  3. 18 Dec, 2018 2 commits
  4. 12 Dec, 2018 3 commits
  5. 07 Nov, 2018 1 commit
  6. 06 Nov, 2018 1 commit
  7. 05 Nov, 2018 3 commits
  8. 02 Nov, 2018 3 commits
  9. 01 Nov, 2018 1 commit
  10. 29 Oct, 2018 3 commits
  11. 24 Oct, 2018 1 commit
  12. 21 Oct, 2018 2 commits
  13. 19 Oct, 2018 1 commit
    • Peter Hutterer's avatar
      quirks: disable debouncing on the VMware Virtual mice · ec5d7702
      Peter Hutterer authored
      At least on MacBooks, the host emulates two clicks 8ms apart in response to a
      doubletap. Those clicks are filtered by our debouncing code.
      
      Since these are emulated devices anyway and by definition cannot have a stuck
      button, let's tag them so we don't enable the debouncing code. If the button
      of the physical device is stuck, that's a problem that needs to be fixed in
      the host system.
      
      Fixes #158
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      ec5d7702
  14. 18 Oct, 2018 1 commit
  15. 16 Oct, 2018 1 commit
    • myfreeweb's avatar
      quirks: use basename in a POSIX compliant way · b0cd07bf
      myfreeweb authored
      The POSIX version of basename modifies the string (and therefore crashes
      on static strings), so use safe_strdup before calling it.
      
      glibc provides a POSIX version when libgen.h is included.
      FreeBSD 12 provides a POSIX version when nothing is included, which was
      causing a segfault.
      
      Using the POSIX version correctly is the right way to avoid any such issues.
      b0cd07bf
  16. 15 Oct, 2018 3 commits
  17. 10 Oct, 2018 1 commit
  18. 08 Oct, 2018 1 commit
  19. 04 Oct, 2018 1 commit
    • Peter Hutterer's avatar
      touchpad: avoid motion events when moving one finger into AREA · df1f6ba4
      Peter Hutterer authored
      If a 2fg scroll motion starts with both fingers in the bottom button area and
      one finger moves into the main area before the other, we used to send motion
      events for that finger. Once the second finger moved into the main area the
      scroll was detected correctly but by then the cursor may have moved out of the
      intended focus area.
      
      We have two transitions where we may start sending motion events: when we move
      out of the bottom area and when the finger moves by more than 5mm within the
      button area. In both cases, check for any touches that are in the
      bottom area and started at the 'same' time as our moving touch. Mark those as
      'moved' to release them for gestures so we get the right finger count and
      axis/gesture events instead of just motion events.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      df1f6ba4