On Sonntag, 13. Februar 2022 04:59:51 CET Fusion Future wrote:
> On 2022/2/13 05:46, Martin Koller wrote:
> > What has changed and how would I now use the new KCM in a KCMultiDialog ?
>
> It can be changed to "kcm_bluetooth". Please see [1] to see if that helps.
>
> [1] https://invent.kde.org/pla
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
n Koller"
Cc: kde-frameworks-de...@kde.org, plasma-devel@kde.org, alexander.loh...@gmx.de
Betreff: Re: kcm_bluetooth changed ?
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 targe
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
On 2022/2/13 05:46, Martin Koller wrote:
What has changed and how would I now use the new KCM in a KCMultiDialog ?
It can be changed to "kcm_bluetooth". Please see [1] to see if that helps.
[1] https://invent.kde.org/plasma/bluedevil/-/merge_requests/49
