1. 09 Nov, 2018 1 commit
  2. 07 Nov, 2018 8 commits
  3. 06 Nov, 2018 1 commit
  4. 05 Nov, 2018 3 commits
  5. 02 Nov, 2018 3 commits
  6. 01 Nov, 2018 1 commit
  7. 29 Oct, 2018 3 commits
  8. 24 Oct, 2018 1 commit
  9. 21 Oct, 2018 2 commits
  10. 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 #158Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
  11. 18 Oct, 2018 1 commit
  12. 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.
  13. 15 Oct, 2018 3 commits
  14. 10 Oct, 2018 1 commit
  15. 08 Oct, 2018 1 commit
  16. 04 Oct, 2018 3 commits
  17. 03 Oct, 2018 4 commits
  18. 02 Oct, 2018 2 commits
    • Peter Hutterer's avatar
      touchpad: ignore motion speed for hovering touches · a8e3f4d1
      Peter Hutterer authored
      tp_detect_thumb_while_moving() assumes that of the 2 fingers down, at least
      one must be in TOUCH_UPDATE, otherwise we wouldn't have a speed to analyze for
      If a touch starts in HOVERING and exceeds the speed limit, we were previously
      increasing the 'exceeded count'. This later leads to an assert() in
      tp_detect_thumb_while_moving() when the second finger comes down because
      although we have multiple fingers, none of them are in TOUCH_UPDATE.
      This only happens when fingers 2 and 3 come down in the same event frame,
      because then we have nfingers_down at 2 (the hovering one doesn't count) but
      we don't yet have a finger in TOUCH_UPDATE.
      Fix this twofold, first by now calculating the speed on anything but
      TOUCH_UPDATE. And second by force-resetting the speed count on
      TOUCH_BEGIN/TOUCH_END so we definitely cover all the hover transitions.
      Fixes #150Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
    • Peter Hutterer's avatar