https://bugs.kde.org/show_bug.cgi?id=370258
--- Comment #12 from Eike Hein <h...@kde.org> --- It's highly undesirable to track stacking order in the Task Manager (and even more so on the QML/JS side) for many reasons: - It's error-prone because it's non-trivial to get right. For example, how does the stacking order of a hidden window relate to shown windows as they get raised and lowered while the window is hidden? This kind of behavior is undefined and differs by window manager, so even if you manage to mimick KWin behavior, ... - It's enormously inefficient. Every window state changes you have yet another process doing stuff in response for something rarely needed. I won't accept it in review (I wrote and maintain all this stuff) so ... I'm not saying there isn't a sane way to do this, but I haven't sat down and done the research on what that way is. It might be interesting to look at how the Mac OS window manager does it, since they were comitted to MDI for a long time and probably have protocols around per-window-set focus planes. -- You are receiving this mail because: You are watching all bug changes.
