since addActivity in layout.js is the wrong place and extremely fragile,
allow to have more than one default activity with custom names
the config key is unchanged so all is retrocompatible, even
if the key being singular isn't 100% correct now
Details
Details
- Reviewers
ivan bshah - Group Reviewers
Plasma - Commits
- R161:6e60c6a3e46b: allow to have more than one default activity
tried with an empty session, works correctly
Diff Detail
Diff Detail
- Repository
- R161 KActivity Manager Service
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
src/service/Activities.cpp | ||
---|---|---|
233 | We'll end up toggling between activities on startup. |
src/service/Activities.cpp | ||
---|---|---|
233 | If the default is "activityA, activityB" I don't want clients (plasmashell) to start loading the layout for activityA and then start loading activityB. |
src/service/Activities.cpp | ||
---|---|---|
233 | when i tested it it didn't seem to switch to the latest created one without an explicit setCurrentActivity? |
src/service/Activities.cpp | ||
---|---|---|
233 | @davidedmundson Haven't looked at that part of Plasma for some time, but I see no reason why it would do that since creating a new activity does not make it current. |
src/service/Activities.cpp | ||
---|---|---|
233 | setActivityState(activity, Running); |
src/service/Activities.cpp | ||
---|---|---|
233 | yeah, my bad. Ignore my comment. |