1. 09 Apr, 2018 1 commit
  2. 20 Mar, 2018 1 commit
  3. 15 Sep, 2017 1 commit
  4. 05 May, 2017 1 commit
  5. 09 Mar, 2017 1 commit
  6. 09 Feb, 2017 1 commit
  7. 12 Dec, 2016 1 commit
  8. 19 Oct, 2016 1 commit
  9. 18 Oct, 2016 1 commit
  10. 30 Sep, 2016 1 commit
  11. 21 Sep, 2016 1 commit
  12. 07 Sep, 2016 1 commit
  13. 31 Aug, 2016 1 commit
  14. 09 May, 2016 1 commit
    • Peter Hutterer's avatar
      Add tablet pad support · 34b6ed98
      Peter Hutterer authored
      Modelled to be mostly compatible to the xf86-input-wacom driver behavior. The
      pad gets 7 axes, the first three of which are mute and the others are always
      available but obviously only send events when the axis is there.
      
      The strip axes are incompatible, the wacom driver merely forwards the device
      events (which are a bitshifted value), libinput normalizes it and we just
      expand this back into an integer range. Let's see how we go with this.
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      34b6ed98
  15. 28 Apr, 2016 1 commit
  16. 07 Apr, 2016 1 commit
  17. 26 Feb, 2016 1 commit
  18. 28 Jan, 2016 1 commit
  19. 23 Dec, 2015 1 commit
  20. 27 Oct, 2015 1 commit
  21. 26 Oct, 2015 1 commit
  22. 17 Sep, 2015 1 commit
  23. 31 Aug, 2015 1 commit
  24. 12 Aug, 2015 1 commit
    • Peter Hutterer's avatar
      Add drag lock support · e3a888c3
      Peter Hutterer authored
      First, why is this here and not in libinput: drag lock should be implemented
      in the compositor (not in libinput) so it can provide feedback when it
      activates and grouped in with other accessibility features. That will work for
      Wayland but in X the compositor cannot filter button events - only the server
      and the drivers can.
      
      This patch adds mostly the same functionality that evdev provides with two
      options on how it works:
      * a single button number configures the given button to lock the next button
        pressed in a logically down state until a press+ release of that same button
        again
      * a set of button number pairs configures each button with the to-be-locked
        logical button, i.e. a pair of "1 3" will hold 3 logically down after a
        button 1 press
      
      The property and the xorg.conf options take the same configuration as the
      evdev driver (though the property has a different prefix, libinput instead of
      Evdev).
      
      The behavior difference to evdev is in how releases are handled, evdev sends
      the release on the second button press event, this implementation sends the
      release on the second release event.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=85577Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
      e3a888c3
  25. 04 Aug, 2015 2 commits
  26. 21 Jul, 2015 1 commit
  27. 14 Jul, 2015 1 commit
  28. 09 Jul, 2015 1 commit
  29. 05 Jun, 2015 1 commit
  30. 20 May, 2015 1 commit
  31. 23 Apr, 2015 2 commits
  32. 06 Mar, 2015 1 commit
  33. 26 Feb, 2015 1 commit
  34. 24 Feb, 2015 1 commit
  35. 27 Jan, 2015 1 commit
  36. 21 Jan, 2015 2 commits
  37. 20 Jan, 2015 1 commit