1. 09 Jan, 2023 1 commit
    • Peter Hutterer's avatar
      Add support for custom pointer acceleration · f94a8edb
      Peter Hutterer authored and Yinon Burgansky's avatar Yinon Burgansky committed
      Adds new properties and xorg.conf entries for setting the acceleration
      function's points and step.
      
      `AccelProfile` option can now accept `custom` value.
      
      Add 4 new options which only apply when `AccelProfile` is `custom`:
      
      - Add `AccelPointsFallback` option for setting the points of the
        Fallback acceleration function. Points values are represented by a
        space-separated list, e.g. "0.0 1.0 2.4 2.5".
      
      - Add `AccelStepFallback` option for setting the step of the Fallback
        acceleration function. When a step of 0.0 is provided,
        libinput default Fallback acceleration function is used.
      
      - Add `AccelPointsMotion` and `AccelStepMotion` options, which are
        equivalent to `AccelPointsFallback` and `AccelStepFallback` options,
        but apply to the Motion acceleration function.
      
      See libinput documentation for a detailed explanation of custom
      pointer acceleration.
      f94a8edb
  2. 08 Dec, 2022 1 commit
  3. 23 Jul, 2022 2 commits
  4. 27 Apr, 2022 1 commit
  5. 25 Jan, 2022 3 commits
  6. 24 Jan, 2022 3 commits
  7. 16 Jan, 2022 2 commits
  8. 18 Dec, 2021 1 commit
  9. 24 Nov, 2021 1 commit
  10. 17 Nov, 2021 1 commit
  11. 14 Nov, 2021 1 commit
  12. 10 Nov, 2021 1 commit
  13. 19 Sep, 2021 1 commit
  14. 16 Sep, 2021 3 commits
  15. 06 Aug, 2021 1 commit
  16. 04 Aug, 2021 2 commits
    • José Expósito's avatar
      Get scroll source in the event handler · ca9042c7
      José Expósito authored
      
      
      Where libinput supports high-resolution scroll events, the scroll source
      is encoded in the event type.
      
      Get the scroll source in xf86libinput_handle_event to facilitate the
      migration.
      
      Refactor, no functional changes.
      
      Signed-off-by: José Expósito's avatarJosé Expósito <jose.exposito89@gmail.com>
      ca9042c7
    • Peter Hutterer's avatar
      Upgrade the default scroll distance to 120 · bf8dc2e2
      Peter Hutterer authored and José Expósito's avatar José Expósito committed
      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.
      
      For non-wheel scrolls we need to now map into the new range. Previously we
      just passed the scroll events on from the touchpad/button scrolling, meaning a
      vdist of 15 meant 15 "libinput pixels" of scrolling resulted in a logical
      wheel click. Now that we have 120 as vdist, we need to times the input data by
      8 to keep the same proportions.
      
      See 39b0bb45
      
       for the previous revert.
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      bf8dc2e2
  17. 05 Jul, 2021 1 commit
  18. 23 Jun, 2021 1 commit
  19. 05 May, 2021 2 commits
    • Peter Hutterer's avatar
      Implement a touchpad scroll distance property · 9bb9e635
      Peter Hutterer authored
      
      
      To be used for touchpads and continuous (i.e. button-based scrolling).
      
      libinput provides us with pixel data for finger-based and button-based
      scrolling but the X server does support this - XI2.1 smooth scrolling is
      merely centered around a logical scroll click (defined as "increment"), with
      smooth scrolling being a fraction of that increment. For example, in the old
      synaptics driver that value was in device-specific units and thus different
      for every device.
      
      The increment is a constant value set in the ScrollClass and cannot be changed
      at device runtime. So we simply initialize with a random default (15, because
      that works well for wheels) and then scale our pixel delta in to that range.
      
      With the default value, a 15 pixel movement would result in a logical scroll
      click, if the distance is set to 30 the users has to move 30 pixels to trigger
      that scroll click. Pixel here being defined as the deltas that libinput
      provides to us.
      
      From the client's perspective nothing changes, the increment is still the
      same.
      
      Range checks are quite restrictive, this option is supposed to improve
      usability, not as a workaround around other bugs.
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      9bb9e635
    • Peter Hutterer's avatar
      Fix a spacing issue · cc10918b
      Peter Hutterer authored
      
      
      yay for copy/paste proliferation
      
      Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
      cc10918b
  20. 16 Apr, 2021 1 commit
  21. 09 Apr, 2021 1 commit
  22. 06 Apr, 2021 3 commits
  23. 24 Mar, 2021 1 commit
  24. 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
  25. 19 Oct, 2020 2 commits
  26. 19 May, 2020 2 commits