https://bugs.kde.org/show_bug.cgi?id=488060
--- Comment #9 from Vaclav Fiala <f...@fedy.cz> --- > A nice rule of thumb (not requiring any specific rules) could probably be > following the PID tree. Does the parent process (or more generally any > ancestor) have focus? Just as I sent the above, I realized that the (more general) ancestor rule probably isn't a good idea. It would certainly require some additional cutoff rules: - Pure direct parent rule would probably work most of the time, but there might be a lot of applications that spawn the new GUI process indirectly (with one or more PIDs in between). - General PID ancestor rule would then fail for example in case of the KRunner: Any application spawned by Krunner could steal the focus in the moments when KRunner is in focus itself. Maybe the ancestor cutoff rule could be the first PID above (including self) that has/had a GUI (window). The idea needs some work for sure. Any counter-examples would help developing it further. -- You are receiving this mail because: You are watching all bug changes.
