D20186: [libinput-touchpad-kcm] Use wayland specific touchpad KCM UI when libinput is used on X11
Fabian Vogt
noreply at phabricator.kde.org
Wed May 15 17:59:31 BST 2019
fvogt added a comment.
In D20186#465586 <https://phabricator.kde.org/D20186#465586>, @ngraham wrote:
> Also keep in mind that it's possible to have global config files in `/etc/X11/xorg.conf.d/` I have one such file there myself that I made to work around the lack of this feature being implemented yet:
>
> $ cat /etc/X11/xorg.conf.d/99-libinput.conf
> Section "InputClass"
> Identifier "libinput touchpad catchall"
> MatchIsTouchpad "on"
> MatchDevicePath "/dev/input/event*"
> Driver "libinput"
> Option "ClickMethod" "clickfinger" # other option is "buttonareas"
> Option "DisableWhileTyping" "false"
> Option "AccelSpeed" "0.2"
> #Option "MiddleEmulation" "true" # Only use this with the "buttonareas" clickmethod
> EndSection
>
>
> Others may have similar settings. If possible, it might be nice to read these config files to determine the default option state in the KCM. Then once the user modifies anything, a new user-specific config file gets written that takes priority.
AFAIK those options are what
In D20186#465670 <https://phabricator.kde.org/D20186#465670>, @atulbi wrote:
> In D20186#465586 <https://phabricator.kde.org/D20186#465586>, @ngraham wrote:
>
> > Also keep in mind that it's possible to have global config files in `/etc/X11/xorg.conf.d/` I have one such file there myself that I made to work around the lack of this feature being implemented yet:
> >
> > $ cat /etc/X11/xorg.conf.d/99-libinput.conf
> > Section "InputClass"
> > Identifier "libinput touchpad catchall"
> > MatchIsTouchpad "on"
> > MatchDevicePath "/dev/input/event*"
> > Driver "libinput"
> > Option "ClickMethod" "clickfinger" # other option is "buttonareas"
> > Option "DisableWhileTyping" "false"
> > Option "AccelSpeed" "0.2"
> > #Option "MiddleEmulation" "true" # Only use this with the "buttonareas" clickmethod
> > EndSection
> >
> >
> > Others may have similar settings. If possible, it might be nice to read these config files to determine the default option state in the KCM. Then once the user modifies anything, a new user-specific config file gets written that takes priority.
>
>
> Is there any specific library which could read these files ??
AFAIK this is not necessary. The configuration here simply specifies the default values for the properties used until overwritten during runtime.
So storing it in whatever format and applying them on device discovery is fine.
REPOSITORY
R119 Plasma Desktop
REVISION DETAIL
https://phabricator.kde.org/D20186
To: atulbi, ngraham, romangg, davidedmundson, #plasma
Cc: fvogt, GB_2, jriddell, knambiar, plasma-devel, jraleigh, ragreen, Pitel, ZrenBot, lesliezhai, ali-mohamed, jensreuterberg, abetts, sebas, apol, mart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20190515/8c4709e6/attachment.html>
More information about the Plasma-devel
mailing list