| |||||||||||||
Focus stealingFocus stealingPosted Aug 18, 2005 14:00 UTC (Thu) by Klavs (subscriber, #10563)In reply to: Focus stealing by corbet Parent article: GNOME and the way forward
Not to be a troll, but that exact feature in KDE, is one of the things that keeps me running KDE.
So it seems it should be doable for Gnome as well.
(Log in to post comments)
Focus stealing Posted Aug 18, 2005 16:37 UTC (Thu) by newren (subscriber, #5160) [Link] In KDE with focus-follows-mouse - you can give a delay - so if you jump past a window (like firefox) the focus is not taken - as long as it is within that configurable delay.Also works for focus-under-mouse and focus-strictly-under-mouse modes, right? Kind of defeats what he requested, though ("why not just have the focus be on the window under the pointer, always?"). Also - if I in konsole start xclock - and the mouse stays over the konsole - xclock does not get focus, simply because it started. KWin has four focus modes, IIRC. Which of them are you using (please check closely as three of them have very similar names)? Also, again IIRC, KWin's level of focus stealing prevention is configurable to 5 levels. To which level have you set it? (If I were to take a guess, I'd say you're using the default level of focus-stealing-prevention and using either the "Focus under mouse" or "Focus strictly under mouse" modes which totally destroy keynav (as claimed by KWin itself). I think adding a "strict" mode to metacity that doesn't focus new windows might make sense but I'd make it somewhat different as I don't think keynav should be ruined in any focus mode) Secondly, note that you can use KWin under Gnome and Metacity under KDE. People have done both. I just point this out because technically you should have said "KWin" instead of "KDE" in your post, though it's unlikely you caused any confusion. ;-)
|
|||||||||||||