summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorPeter Hutterer <peter.hutterer@who-t.net>2019-10-22 12:10:03 +1000
committerPeter Hutterer <peter.hutterer@who-t.net>2019-10-23 08:00:44 +1000
commit8011d991fee4a5e1d9c52cd7809c160e793c1ab7 (patch)
tree76c57494b55552164039b8cca6591d4cab2fa4f1 /doc
parent17ec6ac79d48ad3f1d7290e4698987f860e7cf8f (diff)
downloadlibinput-8011d991fee4a5e1d9c52cd7809c160e793c1ab7.tar.gz
doc/user: add a faq entry about the pointer acceleration "issue"
Despite many bits wasted on reddit, phoronix, lwn etc. no-one seems interested in actually fixing this for their device, so let's at least add a FAQ entry. Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/user/faqs.rst12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/user/faqs.rst b/doc/user/faqs.rst
index 4de7a3fc..7cd6113d 100644
--- a/doc/user/faqs.rst
+++ b/doc/user/faqs.rst
@@ -42,6 +42,18 @@ This is a symptom of an invalid trackpoint multiplier. These devices need
pointer acceleration accordingly. See :ref:`trackpoint_range` for a detailed
explanation.
+.. _faq_pointer_acceleration:
+
+------------------------------------------------------------------------------
+Why is libinput's pointer acceleration worse than synaptics/evdev
+------------------------------------------------------------------------------
+
+This is a known problem affecting some devices and/or use-case but the exact
+cause is still unknown. It may be a device-specific issue, it may be a bug
+in libinput's acceleration code, it may be a disagreement about how pointer
+acceleration should feel. Unfortunately this is something that affected
+users need to investigate and analyze.
+
.. _faq_enable_tapping:
------------------------------------------------------------------------------