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 337755 - Clicking "Unmaximize window" should not resize a window to an essentially maximized size
Clicking "Unmaximize window" should not resize a window to an essentially max...
Status: RESOLVED DUPLICATE of bug 243962
Product: metacity
Classification: Other
Component: general
unspecified
Other All
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2006-04-09 00:52 UTC by Richard Laager
Modified: 2006-04-09 02:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Richard Laager 2006-04-09 00:52:24 UTC 
I've seen this problem on multiple operating systems over the years.... It's
really frustrating and it'd be nice if metacity would be a leader in addressing it.

If I have a window that is maximized, and I click the unmaximize, I expect it to
shrink that window by a non-trivial amount. Sometimes I'll end up with a window
exactly the same size or just a few pixels smaller.

This is happening with Evolution right now. If I click unmaximize, the window
contents become slightly smaller, but the outside dimensions are the same. The
only change has been that the window gets the bordering.


Other information:
Comment 1 Elijah Newren 2006-04-09 01:02:20 UTC 
Unmaximize merely means to return the window to the size it was before it was maximized; not doing that would be a bug.  The only case where we might be able to do something is if the window started out maximized and thus had no "previous size" to return it to.  Is that the case you are observing?
Comment 2 Richard Laager 2006-04-09 01:14:05 UTC 
Yes, that seems to be the scenario which causes this problem.
Comment 3 Elijah Newren 2006-04-09 01:44:26 UTC 
place_window_if_needed() in constrants.c handles the starts-out-maximized problem by making the saved window size be 75% of the available screen size in each direction.  Thus, when you unmaximize, you get a window that is 75% of the screen width and screen height.  Is 25% insufficient?  Or are we possibly looking at the case of an app that does set some weird large size and then almost immediately maximizes itself?
Comment 4 Richard Laager 2006-04-09 02:00:18 UTC 
Well, Evolution is the only example of this I have on hand at the moment.

75% sounds like a good amount in general.
Comment 5 Elijah Newren 2006-04-09 02:07:39 UTC 
That's an Evolution bug.  ;-)

*** This bug has been marked as a duplicate of 243962 ***