Version: unspecified (using KDE 4.6.0) OS: Linux Currently when I switch activities (whether via a keyboard shortcut or the Activity Bar), the same window is always receives the focus. The window in question is a kcalc that I have configured to exist in all activities. It doesn't matter what other window I focus on before switching away from any activity: when I switch back to it, the kcalc window is always the one that receives the focus. Ideally, the full switching stack of each activity would be maintained when switching away from and back to the activity. Reproducible: Didn't try Steps to Reproduce: Create at least two activities with at least one window in each activity (windows A and B), and one additional windows that appears in both (C). Focus on the activity-specific window (A), switch activity, focus again (B), switch back to the original. Actual Results: The shared window (C) now has the focus Expected Results: The previously active window in the activity (A) should have the focus.
plasma does not handle window stacking order.
This is not about the stacking order but about the active client in an activity. This seems to fall into the same category as the current review request to restore the current VD for activities and by this likely belongs to libkactivities (subsession management), yesno? -> reassigning (to plasma, for libkactivities has not component...) for reconsideration.
Honestly, I'd like to remove all kwin-related code from kactivities. kactivitymanager does not do anything with plasma, but it has an ugly entanglement with kwin and ksmserver. So, I'd like this to be in kwin - it is the one remembering which window belongs to which activity, not kamd. Moving to kactivities component until this is decided.
Is this also the reason Knotes always steal focus when switching activities? (and even worse, they're not even raised, so typing goes to a non-visible window)