https://bugs.kde.org/show_bug.cgi?id=501326
--- Comment #5 from cwo <cwo....@posteo.net> --- (In reply to Riccardo Robecchi from comment #4) > I do not see a case in which what we have now is a desirable outcome. I feel > that whatever the chosen approach is, there cannot be a situation in which > clicking on the icon in the task manager does not raise the corresponding > window, because that is simply a broken design. If an exception must be made > in the code in order to make it work, then it should. I'm skeptical because the user specifically set this up - the task manager by default only shows the current desktop, and the default window activation on a different VD is "move to VD" I think. That it appears broken is because the user selected custom options that have a somewhat unfortunate interaction. Sometimes it might make sense to work around this if we can infer what the user is trying to do, or to show a warning. But in this case I see, for example, no principled reason to prefer moving to the VD that the window is on over moving the window to the current VD – and the user has specifically stated that they do not want either to happen. (And it's not like no one could ever want this particular behavior). There's a cost to making settings do unspecified other things even if these are a clear improvement in some cases. For example, the "Mouse wheel cycles through tasks" option has different behaviors depneding on the task that it is, and the feature is more confusing and harder to extend because of it - there are valid feature requests that are stalled on it being essentially impossible to figure out a good wording that actually explains what it does. -- You are receiving this mail because: You are watching all bug changes.
