GNOME Bugzilla – Bug 314915
new windows do not center when overlapping
Last modified: 2005-08-31 04:16:34 UTC
Distribution/Version: Ubuntu Open a window (a gaim conversation for instance) and put it in the center of the screen. Open a big window (such as an epiphany one). Notice how epiphany will always go to the top-left corner. Now, I haven't found any traces of bug reports for this yet, so let me explain why I think it's a bug, with examples. 1- I want to have my windows centered. I just can't stand having two sides cornered while the two others have lots of free space on the screen, showing the desktop. 2- trying to counter this bug, I find myself using epiphany in maximized state for two seconds, before realizing that I cannot stand maximized windows because, without being able to see the desktop acting as a "colorful border", the window simply blends with the taskbars. That's very bad from a visual standpoint I think, because you get more eyestrain trying to make the difference between 4 levels of bars (taskbar, titlebar, menubar, toolbar, adressbar, and so on). KDE has an option to "make the new windows appear centered instead of using a smart placement". However, it would be interesting to just have that as default IF the default placement cannot fit the window in a free space. Otherwise it just makes me crazy having to drag every gaim conversation at the center of the screen. This is one of the remaining few gripes I have while using gnome: new windows always appear on the top-left corner, and I have to do unnecessary moving-around (or eye-stretching).
Thanks for the bug report. Despite being closed, bug 151818 still has a fair amount of discussion on the matter. Since my last post in that bug, I thought of something else that I think we improve on it (more hybrid behavior that I haven't seen suggested elsewhere), but anyway, this specific case is discussed. I should probably open a new bug with the relevant info, but either way, I'm not losing track of that bug and I'd like to keep these two linked so I'm going to mark this one as a duplicate. *** This bug has been marked as a duplicate of 151818 ***