but then i have to compile the whole plasma framework. that’s far out of scope of a plasma applet :/
2014-12-28 0:57 GMT+01:00 David Edmundson <da...@davidedmundson.co.uk>: > > > On Sat, Dec 27, 2014 at 10:11 PM, Philipp A. <flying-sh...@web.de> wrote: > >> Hi, >> >> i’m developing a plasma wiget with C++ plugin. >> >> consistent with how upstream packages do it, with my package being called >> `org.kde.plasma.steam`, the plugin is called `org.kde.plasma.private.steam`. >> >> i try to load my plasmoid from its dev directory via >> >> QML2_IMPORT_PATH="../build/:$QML2_IMPORT_PATH" plasmoidviewer "$@" . >> >> now my problem is that the following seems to be triggered: >> >> >> https://projects.kde.org/projects/frameworks/plasma-framework/repository/entry/src/plasmaquick/packageurlinterceptor.cpp?rev=master#L128 >> >> i.e. `path().contains("org/kde/plasma/private")`, so `pathCheck` should >> be replaced with `org.kde.plasma.steam`. but why does the following test >> fail? `pathCheck == m_package.metadata().pluginName()` >> > > From the information given, I have no idea. > > I recommend adding qDebug statements all over that method till the > problem reveals itself. > > > >> >> the plasmoidviewer should load the app metadata, which clearly states >> `X-KDE-PluginInfo-Name=org.kde.plasma.steam` >> >> >> https://projects.kde.org/projects/extragear/sdk/plasmate/repository/revisions/frameworks/entry/plasmoidviewer/view.cpp#L105 >> >> _______________________________________________ >> Plasma-devel mailing list >> Plasma-devel@kde.org >> https://mail.kde.org/mailman/listinfo/plasma-devel >> >> > > _______________________________________________ > Plasma-devel mailing list > Plasma-devel@kde.org > https://mail.kde.org/mailman/listinfo/plasma-devel > >
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel