| hein |
| Plasma on Wayland | |
| KWin |
Device gets a KConfigGroup injected and supports loading device-specific
settings. This is invoked from Libinput::Connection when adding a new
Device.
Whenever a Device option is changed successfully through the DBus
interface it gets synced into the KConfigGroup, thus on next loading of
the Device it gets restored.
The config group follows a pattern of:
[libinput][vendor][product]
Thus every device has a specific and persistent configuration.
So far only tested through autotests
| Automatic diff as part of commit; lint not applicable. |
| Automatic diff as part of commit; unit tests not applicable. |
It's funny (is it?) that I'm just doing the same. I should have told you I guess :)
Your solution is simpler anyway. My solution involves inputdevice.kcfg.
I don't think the [vendor][product] key is sufficient. I have two DELL devices here with the same product code, but different name and different functionality. I suggest the key to be [vendor][product][name].
I also wanted to use kcfg in the first place, but as it's difficult to inject the KConfigGroup I decided against and came up with the slightly too complex template magic.
Works for me.
[Libinput][1133][50184][Logitech USB Trackball] MiddleButtonEmulation=true ScrollButton=275 [Libinput][1739][30171][DLL0675:00 06CB:75DB Touchpad] TapToClick=true