| Summary: | Different settings/style is exposed based on the system | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Claudius Ellsel <claudius.ellsel> |
| Component: | kcm_mouse | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
| Status: | RESOLVED INTENTIONAL | ||
| Severity: | normal | CC: | claudius.ellsel, nate, unassigned-bugs |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Claudius Ellsel
2018-11-30 18:07:43 UTC
This is intentional, because the mouse KCM has two backends: Evdev and Libinput. They expose different features, and therefore need different user interfaces. The current touchpad KCM attempts to use the same interface for multiple backends and it's super confusing, since most things are grayed out when using Libinput, and a lot of its features aren't exposed at all. Alright. Thanks for the explanation! |