Registered Member
|
Now that activities seem to get more useful since 4.6.x, I wanted to give it another try. It seems it's possible to assign your application to specific activities. When you stop an activity the app is closed down and restarted when you resume the activity again.
However one thing which seem useful is that each activity (except some default, say the last) is deactivated by default and as soon when you an activity is activated (say after a login) all the previously assigned applications restart also. Currently it seems activities are always active and all the previous assigned applications are not restarted and must be reassigned after every logout. Or am I missing something here? |
Administrator
|
You are correct. The association activity/application is still runtime only, mainly because the API to implement this in applications (so that it can be used by developers) is not yet stable or complete.
As far as I can see, the Plasma developers will start tackling the issue either in the upcoming Tokamak sprint, or in the kdelibs (Platform 11) sprint later this year.
"Violence is the last refuge of the incompetent."
Plasma FAQ maintainer - Plasma programming with Python |
Registered Member
|
Alright I'll postpone it a little more then. Thanks for your reply
|
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]