16

When switching activity, I would love to be taken to the desktop I left in the new activity, instead of the one I left in the old activity.

Hm, I will make an example: I'm in desktop 1 in the Photo activity, then I switch to the Desktop activity and arrives to desktop 1. I switch to desktop 2 to use a window there, and then goes back to the Photo activity. There, I arrive at desktop 2, so I have to switch to desktop 1 to continue my work there.

In the last step, I think when switching back to the Photo activity, I should arrive where I left it, at desktop 1!

+1 (when this gets approved).
Virtual desktops should belong to the activity thus enforcing that each activity is a self-contained environment which will be resumed in the exact same state as you left it (this could also allow such craziness as having different virtual desktop setup per activity, but that would be crazy). Right now it seems that virtual desktops are kind of part of/subordinate to activities, but kind of independent/distinct.

I would personally consider this a bug, but I will wait for a second opinion before closing it.

TheBlackCat wrote:I would personally consider this a bug, but I will wait for a second opinion before closing it.

Ack, it obviously sould work as described here. A feature request at least. I posted here to do things in a positive way

After 3 days of using activities, I have decided that this is a bug. It is simply bad workflow not to be taken to the right virtual desktop.

report is here: https://bugs.kde.org/show_bug.cgi?id=265015

Marked as submitted, please use https://bugs.kde.org/show_bug.cgi?id=265015 to vote and for further discussion.

I had this quick mockup proposal with another solution to address the issue you mention.

And here's the idea to vote for it :
brainstorm.php#idea94324_page1

I have just updated to 4.6 (because of activities) and started to set up activities, but immediately run into this annoying bug. I hope it will be fixed soon, because the concept of activities is great, but this problem is a pain. For me it seems that the developers of activities didn't think of them originally as really independent workflows.

I believe this was fixed in https://bugs.kde.org/show_bug.cgi?id=241864