https://bugs.kde.org/show_bug.cgi?id=461118
--- Comment #2 from Richard J. Acton <richardjac...@pm.me> --- (In reply to Eric Edlund from comment #1) > This is interesting material. I threw this into the Activities group chat > and we learned a few things which I will note here. > > Switching windows between activities is something we want design away from. > The point of activities is to separate activities. The need to move windows > between them will, of course, always be a need that we can't completely > design away. Keyboard shortcuts may be a good idea. > > We still have a lot to figure out about windows being on multiple activities > in multiple desktops if activities end up having unique sets of VDs. It > won't be an issue of just which activity but which desktop windows are shown > on. Keeping the distinction between activities and desktops clear will be > tricky. Thanks Eric, I'm new here so I'm not sure if this is suitable for a thread under the issue or might be better placed in the activities chat that you mentioned (is that a matrix room or something that I could join?) I don't generally like moving windows between activities either I prefer to have the right ones for the activities show up there by default in my preset kwin rules but as I mentioned web-browser windows always seems to end up being hard to pre-allocate to the right activity (at least for me) and then it's quite high friction to move them around, hence my interest in keyboard shortcuts to do so. Activity specific VDs are not something I'd thought about up till now. This is an example of how I've used activities and virtual desktops together that might be relevant for the separate VDs by activity question. I usually have a 'comms' activity with all my email and chat clients. I'll put my main email on my primary VD and my chat clients on another. But for example Discord is visible by default in both 'comms' and 'Gaming' activities because it's the chat client I'm most likely to use whilst gaming. However Discord is usually on my secondary VD in 'comms'. Though I'd prefer for Discord to be on my primary VD whilst gaming over on my second monitor so activity specific VD options and window associations could be good for this kind of situation. Coming up with an intuitive default behaviour for a window made visible in an activity which has different VDs would be a challenge. Which VD(s) should it be visible on if there is no VD in common between the activities that they are visible on? Maybe this is bad conceptual mapping though and I should have a different VD for comms in every activity tailored to the comms tools needed in each activity not a central comms activity. -- You are receiving this mail because: You are watching all bug changes.
