Skip to content
Snippets Groups Projects
  1. Dec 08, 2015
  2. Dec 07, 2015
  3. Dec 02, 2015
  4. Nov 15, 2015
  5. Nov 09, 2015
  6. Nov 01, 2015
  7. Oct 30, 2015
  8. Oct 28, 2015
  9. Oct 26, 2015
  10. Sep 18, 2015
  11. Sep 10, 2015
    • Peter Hutterer's avatar
      configure.ac: bump to 1.0.901 · 1d0a1d57
      Peter Hutterer authored
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      1d0a1d57
    • Peter Hutterer's avatar
      Add an API to change pointer acceleration profiles · 8d9e7a1b
      Peter Hutterer authored
      The quartett of new config functions is:
      	libinput_device_config_accel_get_profiles
      	libinput_device_config_accel_get_profile
      	libinput_device_config_accel_set_profile
      	libinput_device_config_accel_get_default_profile
      
      The profile defines how the pointer acceleration works, from a very high-level
      perspective. Two profiles are on offer, "adaptive", the standard one we have
      used so far and "flat" which is a simple multiplier of input deltas and
      provides 1:1 mapping of device movement vs pointer movement.
      
      The speed setting is on top of the profile, a speed of 0 (default) is the
      equivalent to "no pointer acceleration". This is popular among gamers and
      users of switchable-dpi mice.
      
      The flat profile unnormalizes the deltas, i.e. you get what the device does
      and any device below 800dpi will feel excruciatingly slow. The speed range
      [-1, 1] maps into 0-200% of the speed. At 200%, a delta of 1 is translated
      into a 2 pixel movement, anything higher makes it rather pointless.
      
      The flat profile is currently available for all pointer devices but touchpads.
      
      https://bugs.freedesktop.org/show_bug.cgi?id=89485
      
      
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarHans de Goede <hdegoede@redhat.com>
      8d9e7a1b
  12. Sep 09, 2015
    • Peter Hutterer's avatar
      Fix leaking device groups · 0c7ef582
      Peter Hutterer authored
      
      If a caller has a reference to a device group when the context is destroyed,
      the memory for the group is never released. Calling
      libinput_device_group_unref() will release it and there are no side-effects
      since the group has no back-references. It's inconsistent with the rest of
      libinput though - all other resources get released on libinput_unref().
      
      Signed-off-by: default avatarPeter Hutterer <peter.hutterer@who-t.net>
      Reviewed-by: default avatarJonas Ådahl <jadahl@gmail.com>
      0c7ef582
  13. Sep 07, 2015
  14. Sep 06, 2015
  15. Sep 04, 2015
  16. Aug 31, 2015
  17. Aug 26, 2015
  18. Aug 23, 2015
  19. Aug 22, 2015
  20. Aug 21, 2015
  21. Aug 19, 2015
Loading