Disable or Hide an Activity

In the Activities configuration panel (System Settings->Apps & Windows->Activities) I would like to be able to disable or hide an Activity without deleting it.

A disabled Activity would not appear in the Activity Pager widget or in the Activity Manager and could not be switched to.

My use case is that I have an Activity for working on my income taxes. Once they are filed, I would like to be able to disable this Activity until tax time next year.

Interesting idea.

I don’t really mind having an less often used activity available but I usually switch with keyboard short cuts.

In your scenario, how would you handle windows/applications which running on that activity when you disable/hide it?

Thanks for the response. I usually switch activities by mouse wheel, so often have to roll through unused activities.

Just as a test, I created a new activity, opened a konsole window in it, switched to a different activity, then deleted the new activity in System Settings. The konsole window just moved to the current activity. So maybe disabling an activity with windows running could work the same way.

wouldn’t that defeat the purpose of having the activity?

now you would need to reopen all the applications and windows as if creating a new activity from scratch… unless i’m missing something.

when i first read your use case it sounded as tho you wanted to be able to pick up where you left off, but not have to scroll thru it the other 11 months out of the year, like maybe an eyeball control next to the delete button or something.

i don’t know what normally happens to apps in an activity when it is not currently active, but i would think it would be exactly like that, only hidden from the scroll when scrolling the currently visible activities.

Normally, just turning off an Activity will ‘store’ the open windows there, so turning it back on brings thing back to the previous state. Scrolling through these will skip the closed ones.

However, if you reboot with an Activity closed, any apps that were open there will open on your current Activity (if you use the defualt desktop session restore setting), or won’t be restored (if desktop session restore is not used). So the missing feature is a per-Activity session restore option, maybe?

That would be a handy feature, I think. I would use it.
(and at the same time bring back per-Activity panels!! :rofl:)

2 Likes

Yes, my use case is that I will not need the activity for another year and I wanted it to disappear from all the ways of cycling through activities, without having to delete and then re-create it a year from now.

I did not think of the possibility of having open windows in an activity when it is disabled. I guess if you were planning on re-enabling the activity before re-booting, that could be useful.

activities are still a rather doughy feature of plasma, but i think it has a great deal of potential.

the more it can be like a completely separate “user” of your plasma installation, the better in my mind.

so in a perfect world you would be able to restore an activity 11 months later and everything would open up right where you left it ready to go, just like logging back into the desktop with session restore turned on.

this would require a separate set of plasma .config files and some way to manage / duplicate settings across activities similar to how we have to manually back up and copy our .config for a new install of plasma.

for me, in the meantime, i just have a text document with a check list of things i need in order to prepare my taxes and i work thru that using my current desktop/activity.

i suppose i could create a separate user acct “taxes” and clone my plasma setup to it for a distraction free plasma desktop with session restore turned on and all the apps and tools i need open… but i’m too lazy to bother.

If I remember correctly an earlier implementation of Activities even had the capability of starting/stopping them.

Since that is no longer the case that might have caused hard to solve problems.

However this could also have been partly because X11 session management was only ever designed to restore one session.

My interpretation of discussions around Wayland session restore is that it is designed to handle multiple sessions, even per-app “sessions” (so restoring multiple windows of a single app at the previous locations)