After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 108706 - clicking close button causes restacking
clicking close button causes restacking
Status: RESOLVED FIXED
Product: metacity
Classification: Other
Component: general
2.4.x
Other Linux
: Normal major
: METACITY2.6.x
Assigned To: Metacity maintainers list
Metacity maintainers list
: 115846 268975 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-03-18 21:21 UTC by Dan Winship
Modified: 2005-10-11 21:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description Dan Winship 2003-03-18 21:21:53 UTC 
When you click the "close" button on a window now, metacity restacks
windows so that the next window up will be the next available window in
the same application. (I find this behavior annoying, but that's a
separate issue and I assume it was changed to be more like Mac/Win.)
But the particular way that it does this is messy and confusing.

Eg, if you click "close" on an evolution composer window, metacity
restacks the main evo window to the top, and *then* pops up the "are
you sure you want to close the composer" window above it. This causes
a sort of light mental whiplash; the reappearance of the main window
signals "you can stop thinking about the composer now", but then just
as you're starting to plan your next stop, bam! there's the composer
again.

What should happen is, you click "close", the composer pops up its
"save changes?" window, you click "no", the composer window goes away.
and *then* metacity restacks the other window into place.
Comment 1 Havoc Pennington 2003-03-18 21:46:09 UTC 
If I understand this correctly, the problem is just that when you 
click close then we immediately activate another window. But 
we should activate the other window when the window closes, not 
when you click close.
Comment 2 Dan Winship 2003-03-18 22:18:57 UTC 
yes
Comment 3 Havoc Pennington 2003-09-25 03:24:07 UTC 
This is kind of irritating and I don't really remember why we added
the extra logic to work like this. Maybe cvs annotate could be used to
locate the relevant ChangeLog.

To fix you just remove the focus_mru_window from meta_window_delete,
very straightforward. Let's just do that and see who complains.
Comment 4 Havoc Pennington 2003-09-29 17:37:19 UTC 
I checked in this change, if it breaks please open a new bug about the
specific breakage.
Comment 5 Mark McLoughlin 2003-10-08 16:00:36 UTC 
*** Bug 115846 has been marked as a duplicate of this bug. ***
Comment 6 Elijah Newren 2005-10-11 21:22:30 UTC 
*** Bug 268975 has been marked as a duplicate of this bug. ***