1. 12 Aug, 2019 3 commits
  2. 31 Jul, 2019 2 commits
  3. 30 Jul, 2019 1 commit
    • Peter Hutterer's avatar
      Revert "Upgrade the default scroll distance to 120" · 39b0bb45
      Peter Hutterer authored
      This was part of the high-resolution wheel work that was factored out ahead of
      time. Problem is: this breaks scroll button emulation in the server as we
      use the distance to determine when we click buttons 4-7.
      
      Before: movement of 15 normalized pixel units on a touchpad - one click. Now:
      120 of those units. So that's a bit less than ideal.
      
      The change to 120 can be done, but needs the corresponding handling in the
      axis distance calculations.
      
      Fixes #24
      
      This reverts commit 05548118.
      39b0bb45
  4. 25 Feb, 2019 1 commit
    • David Rosca's avatar
      Also use type to match tablet tool with device · 8923d18d
      David Rosca authored
      On devices with tools having both serial and id 0,
      it would fail to create separate subdevices.
      
      Thinkpad X220T (Wacom ISDv4 E6) now correctly registers
      Pen and Eraser xinput devices.
      8923d18d
  5. 12 Feb, 2019 1 commit
    • Peter Hutterer's avatar
      Upgrade the default scroll distance to 120 · 05548118
      Peter Hutterer authored
      This is just a number, to be used as divider and shouldn't have any effect in
      correctly written clients. With the high-res scrolling coming up however, we
      have a few devices where the dist cannot be expressed as an integer fraction
      of 15, so let's up it to 120 because we know all hardware wheels have to be an
      integer fraction of that that, thanks to Microsoft's API requirements.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      05548118
  6. 04 Feb, 2019 1 commit
  7. 25 Jan, 2019 1 commit
    • Peter Hutterer's avatar
      Handle scroll wheel events with a discrete of 0 · e7eafa19
      Peter Hutterer authored
      The driver currently assumes that any wheel event has a non-zero discrete
      value of 1. This is incorrect, it just hasn't triggered yet with any device.
      
      With the hi-res scroll patches in place in the kernel and libinput, we may get
      wheel events with a discrete value of 0. We assume that if this ever happens,
      the device has some sensible click angle set so all we need to do is ignore
      the discrete 0 events and wait for the first discrete event to come.
      
      Also add an explanatory comment too to make it clear the calculation is only
      done once.
      
      Fixes #19
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      e7eafa19
  8. 23 Jan, 2019 1 commit
  9. 21 Jan, 2019 1 commit
  10. 07 Jan, 2019 1 commit
  11. 25 Nov, 2018 1 commit
  12. 18 Nov, 2018 1 commit
  13. 15 Oct, 2018 1 commit
  14. 14 Oct, 2018 1 commit
  15. 04 Oct, 2018 1 commit
  16. 19 Jul, 2018 1 commit
  17. 11 Jul, 2018 2 commits
  18. 10 Jul, 2018 1 commit
  19. 22 May, 2018 1 commit
  20. 02 May, 2018 1 commit
  21. 20 Apr, 2018 2 commits
  22. 17 Apr, 2018 2 commits
  23. 09 Apr, 2018 1 commit
  24. 22 Mar, 2018 1 commit
  25. 20 Mar, 2018 2 commits
  26. 20 Feb, 2018 1 commit
    • Peter Hutterer's avatar
      Apply the capabilities checks on subdevices when applying the config · 9d9f59fd
      Peter Hutterer authored
      Properties are initialized on the correct devices only but on resume we'd just
      blindly apply the config from our device. Depending on the resume order, this
      would mean we'd apply a previously set config with a default config.
      
      Example:
      * pointer device with keyboard subdevice
      * pointer device exports natural scrolling, keyboard device does not and
        remains at default (off)
      * client enables natural scrolling on the pointer device
      * VT switch away, VT switch back
      * pointer device gets enabled first, enables natural scrolling on the
        libinput device
      * keyboard device gets enabled second, resets to the default value
      Reported-by: yshui's avatarYuxuan Shui <yshuiv7@gmail.com>
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Tested-by: yshui's avatarYuxuan Shui <yshuiv7@gmail.com>
      9d9f59fd
  27. 02 Feb, 2018 2 commits
  28. 15 Sep, 2017 1 commit
  29. 17 Aug, 2017 1 commit
  30. 28 May, 2017 1 commit
  31. 18 May, 2017 1 commit
  32. 15 May, 2017 1 commit