the panel tamplates are listed with kpackage listing
but were still loaded with kservicetypetrader
this made possible to have templates listed but not possible
to be loaded. This ports the template loading to the same logic
of the template listing, making thisgs consistent here
Details
Details
- Reviewers
davidedmundson - Group Reviewers
Plasma - Commits
- R120:30a874c89cd7: port panel loading away from ksycoca
R871:30a874c89cd7: port panel loading away from ksycoca
Diff Detail
Diff Detail
- Repository
- R120 Plasma Workspace
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Comment Actions
the emtpy system tray (desktop right click add panel) shouldn't be a panel cause it doesn't work like a panel.
shell/scripting/scriptengine_v1.cpp | ||
---|---|---|
490 | I'm a bit lost. We have an argument to this method which is stored as local QString layout. The old code found all Plasma/LayoutTemplates with that name. (and if we're not using layout, why are we still checking it on line 483) |
Comment Actions
- actually check the panel plugin id
shell/scripting/scriptengine_v1.cpp | ||
---|---|---|
490 | actual plugin name now checked (and the application name isn't something really used anymore) |
shell/scripting/scriptengine_v1.cpp | ||
---|---|---|
488–492 | if you do &layout you'll save doing a copy every time |