LucidTouchpadConfig
Launchpad Entry: touchpad-config-kde
Created: 2009-09-30
Contributors: roderick-greening
Packages affected:
Summary
KDE is currently missing a way to easily configure a touchpad for advanced options like scroll area, disable touchpad while typing, etc.
KDE should have a kcm module for configuring this, as well as some applet to change some simple things like enable/disable, etc. This used to be provided by the qsynaptics package, which is no longer maintained and is only for KDE/QT 3.X.
Release Note
touchpad-config-kde provides a kcm config module for KDE, allowing the end-user to tweak their laptop touchpad and modify advanced settings like multi-touch, disable while typing, etc. Additionally, this package will provide an applet to control the most common functions of the touchpad (enable/disable for example).
Rationale
For most users, the default Xinput settings for their touchpad will be adequate. However, there are cases where advanced settings would be beneficial to tweak how their touchpad behaves. This becomes especially important for things like multi-touch or multi-tap, defining scroll areas, setting sensitivity, etc. Some laptops also have misbehaving touchpads, that are too sensitive with their default settings (e.g. Dell Mini 10v). Allowing the user an easy way to adjust these settings will result in a better overall user experience.
User stories
Assumptions
Touchpad interface is exposed via xinput. The kcm module will interface with xinput to get/set touchpad settings.
Design
Both the kcm module and the applet will be written in PyKDE, which will allow a great deal of flexibility and rapid development.
Implementation
Create a kcm module to load and set touchpad settings. The applet will control talking to xinput and ensure the settings are loaded from kconfig. kcm module should enable turning on/off the applet so the user does not need to search for it and add it to their Autostart.
UI Changes
None: This is a new package.
Code Changes
None: This is a new package.
Migration
None: This is a new package and a previous way has not existed up to this point.
Test/Demo Plan
TODO: complete test plan after spec approved and work has been started
Unresolved issues