mirror of
https://gitlab.freedesktop.org/libinput/libinput.git
synced 2025-12-20 10:20:10 +01:00
doc: add a FAQ regarding "please add a configuration option"
Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
cad73f4023
commit
c67b74b45e
1 changed files with 14 additions and 0 deletions
14
doc/faqs.dox
14
doc/faqs.dox
|
|
@ -125,6 +125,20 @@ Changes performed by xinput do not persist across device hotplugs. xinput is
|
|||
considered a debugging and testing tool only and should not be used for
|
||||
permanent configurations.
|
||||
|
||||
@section faq_configuration Can you add a configuration option for $FEATURE?
|
||||
|
||||
No. At least that's going to be the initial answer. Read <a
|
||||
href="http://who-t.blogspot.com/2016/04/why-libinput-doesnt-have-lot-of-config.html">Why
|
||||
libinput doesn't have a lot of configuration options</a> first.
|
||||
Configuration options for most features are a signal that we are incapable
|
||||
of handling it correctly. To get to that point, we want to be sure we're
|
||||
truly incapable of doing so. libinput has several features that
|
||||
are handled automatically (and correctly) that users wanted to have
|
||||
configuration options for initially.
|
||||
|
||||
So the answer to this question will almost always be 'no'. A configuration
|
||||
option is, in most cases, a cop-out.
|
||||
|
||||
@section faq_synclient Why don't synclient and syndaemon work with libinput?
|
||||
|
||||
Synclient and syndaemon rely on X input device properties that are specific
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue