1. 05 May, 2021 1 commit
  2. 16 Apr, 2021 1 commit
  3. 09 Apr, 2021 1 commit
  4. 06 Apr, 2021 3 commits
  5. 24 Mar, 2021 1 commit
  6. 04 Nov, 2020 1 commit
    • Dorian Stoll's avatar
      Lift canceled touch inputs · 39be9449
      Dorian Stoll authored
      
      
      If a touch input gets turned into a palm (by setting ABS_MT_TOOL_TYPE to
      MT_TOOL_PALM), libinput will emit a cancel event instead of the normal
      up event. The xorg wrapper needs to be able to handle a canceled touch
      and lift it, otherwise these inputs will never get lifted and will stick
      around forever.
      Signed-off-by: Dorian Stoll's avatarDorian Stoll <dorian.stoll@tmsp.io>
      39be9449
  7. 19 Oct, 2020 2 commits
  8. 19 May, 2020 5 commits
  9. 11 Oct, 2019 1 commit
  10. 12 Aug, 2019 3 commits
  11. 31 Jul, 2019 2 commits
  12. 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
  13. 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
  14. 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
  15. 04 Feb, 2019 1 commit
  16. 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
  17. 23 Jan, 2019 1 commit
  18. 21 Jan, 2019 1 commit
  19. 07 Jan, 2019 1 commit
  20. 25 Nov, 2018 1 commit
  21. 18 Nov, 2018 1 commit
  22. 15 Oct, 2018 1 commit
  23. 14 Oct, 2018 1 commit
  24. 04 Oct, 2018 1 commit
  25. 19 Jul, 2018 1 commit
  26. 11 Jul, 2018 2 commits
  27. 10 Jul, 2018 1 commit
  28. 22 May, 2018 1 commit
  29. 02 May, 2018 1 commit