From kde-frameworks-devel  Sun Feb 13 21:01:25 2022
From: Martin Koller <kollix () aon ! at>
Date: Sun, 13 Feb 2022 21:01:25 +0000
To: kde-frameworks-devel
Subject: Re: Aw: Re: kcm_bluetooth changed ?
Message-Id: <7379155.cTIIhqV5Im () lapi>
X-MARC-Message: https://marc.info/?l=kde-frameworks-devel&m=164478702721510

On Sonntag, 13. Februar 2022 19:27:22 CET Alexander.Lohnau@gmx.de wrote:
> Hello,
> =20
> Usually the KCMs are opened by starting kcmshell or systemsettings with t=
he 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 module name prepended, consequ=
ently "kcmshell5 bluetooth" works in both Plasma 5.23 and 5.24.
> =20
> > If KDE/plamsa is such a moving target where  can not rely on compatibil=
ity even between minor versions, that is really not fun
> =20
> Looking at liquidshell, there are multiple  cases where the available KCM=
s are checked at runtime to be compatible with old Plasma versions. While h=
aving to do this is not ideal, it is not anything new.
> Luckily most of the changes to port the KCMs to the new metadata approach=
 have already landed.
> The KWin KCMs remain though, when porting those I will make sure to creat=
e a accompanying MR in liquidshell.

thanks!

> PS: You can check if the KPluginMetaData object is valid, instead of chec=
king if the name is not empty :).

ok. I took the code I was told works ...

=2D-=20
Best regards/Sch=F6ne Gr=FC=DFe

Martin
A: Because it breaks the logical sequence of discussion
Q: Why is top posting bad?

()  ascii ribbon campaign - against html e-mail=20
/\                        - against proprietary attachments

=46r=FChst=FCck, Geschenkideen, Accessoires, Kulinarisches: www.lillehus.at