a0b9a2131c
We were using the plugin infrastructure to tell the name of the plugin we were configuring. Since this doesn't make any sense, just let the kcms themselves define where they want their settings to be. This fixes a regression from when we ported away from using KService to list them. |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
kdeconnect_runcommand.json | ||
kdeconnect_runcommand_config.qml | ||
runcommand_config.cpp | ||
runcommand_config.h | ||
runcommandplugin.cpp | ||
runcommandplugin.h |