Canonical input driver settings #480
metux
started this conversation in
2 RFCs of the Core Team
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the idea
Several input drivers have various driver specific settings (input device properties), which are only valid to certain specific driver.
Thus clients (eg. session managers) need to support all of those (for each individual driver) and also probe which drivers are actually running, in order to practically make use of them.
Instead we should standardize those (which make sense for multiple drivers / device types) into generic ones (eg. mouse acceleration, tap times, etc, etc), which all drivers (where those make sense) support.
Plan:
It should be done because
Standardization of currently drivers specific properties - decouple clients from driver specifics.
What are the alternatives?
No response
Additional context
No response
Extra fields
Beta Was this translation helpful? Give feedback.
All reactions