https://bugzilla.novell.com/show_bug.cgi?id=331835#c14
--- Comment #14 from Federico Mena Quintero
Haven't used it a whole lot, but it seems to be working great! I think the time span is bigger now, right? Thanks. But it does still get the focus after some time, as it should.
It's not a time span, actually. What happens now is: 1. If a window gets mapped but it doesn't have _NET_WM_USER_TIME set, Metacity generates a timestamp for it. 2, If a *transient* window appears but doesn't have a timestamp, Metacity will see if its transient parent has a timestamp that it can use. (1) helps with apps launched without startup-notification, like when you run yast2 from a terminal. (2) helps with evil transient dialogs that appear without any user interaction.
Now, I am under the impression that in Metacity 2.18, when a popup doesn't get focus, its main-window entry on the taskbar gets highlight (you know, just like when you launch an app). But maybe I am wrong here, I need to test that. In any case, as you had to dig around to get to the bug, maybe that would be some easy thing to implement?
That is correct, and it happens as well with this patch.
on :)). First, the window placement strategy. Is there any strategy to it actually? :/ A lot of times, it actually overlaps the new window over your current one, when there is enough room on the screen to put it somewhere else.
You can track this upstream at http://bugzilla.gnome.org/show_bug.cgi?id=155460
The second is the maximization action. Most times, you just want to vertically maximize the window, so middle-click on the maximize button should do it (like
You can track this upstream at http://bugzilla.gnome.org/show_bug.cgi?id=358674 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.