On Sonntag, 13. Februar 2022 19:27:22 CET alexander.loh...@gmx.de wrote:
> Hello,
>
> Usually the KCMs are opened by starting kcmshell or systemsettings with the
> module names as arguments,
> meaning we resolve the location of the KCMs internally and don't require
> changes for consumers. kcms
Hello,
Usually the KCMs are opened by starting kcmshell or systemsettings with the module names as arguments,
meaning we resolve the location of the KCMs internally and don't require changes for consumers. kcmshell also checks if the plugin id
would match if the "kcm_" prefix is to the modul
On 2022/2/13 21:31, Martin Koller wrote:
But still I wonder if such a change is something like breaking ABI
compatibility.
If KDE/plamsa is such a moving target where I can not rely on compatibility even
between minor versions, that is really not fun.
Perhaps the breakage is due to these comm
On Sonntag, 13. Februar 2022 14:15:09 CET Fusion Future wrote:
> On 2022/2/13 20:20, Martin Koller wrote:
> > I already tried this but it did not solve the issue.
>
> This code snippet works on my system. Please have a try.
>
> ```cpp
> dialog = new KCMultiDialog();
>
> KPluginMetaData
> module
On 2022/2/13 20:20, Martin Koller wrote:
I already tried this but it did not solve the issue.
This code snippet works on my system. Please have a try.
```cpp
dialog = new KCMultiDialog();
KPluginMetaData
module(QPluginLoader("plasma/kcms/systemsettings/kcm_bluetooth"));
if (!module.name().i
