On Thu, Aug 4, 2016 at 1:26 PM, Jonathan Riddell wrote:
> On Wed, Aug 03, 2016 at 07:30:21PM +0200, Kai Uwe Broulik wrote:
>> Follow up: i misread the mail, it does work, right? It's just Harold's thing
>> doesn't find it?
>>
>> I didn't want to make another installed qml plugin as the kcm itself
On Wed, Aug 3, 2016 at 7:30 PM, Kai Uwe Broulik wrote:
> Follow up: i misread the mail, it does work, right? It's just Harold's thing
> doesn't find it?
Dat name.
But yes. With runtime injected modules it can't find them as being
present (basically the check runs through all default module path
On Wed, Aug 03, 2016 at 07:30:21PM +0200, Kai Uwe Broulik wrote:
> Follow up: i misread the mail, it does work, right? It's just Harold's thing
> doesn't find it?
>
> I didn't want to make another installed qml plugin as the kcm itself is
> already one. I probably could have just exposed the KCM
Follow up: i misread the mail, it does work, right? It's just Harold's thing
doesn't find it?
I didn't want to make another installed qml plugin as the kcm itself is already
one. I probably could have just exposed the KCModule itself as context property
and access the models from there.
I can
Hi,
that import is registered in the KCModule's constructor, it is *not* an
installed traditional qml plugin.
Also it seems rather it's looking for the kcm's cpp plugin itself? At least the
QML is loading it seems. I don't know how that KCModule QML stuff works, Marco
came up with that :/
Che
Harald did a nifty qml dep checker for neon. Looking at KInfoCenter it asks for
org.kde.kinfocenter.energy.private
but I'm not convinced that exists
possibly not by coincidence I get errors running the energy module in
kinfocenter
org.kde.kcoreaddons: Error loading plugin "kcm_energy
