GNOME Bugzilla – Bug 302204
Maximize-vertically short cut acts as maximize
Last modified: 2005-06-19 15:43:40 UTC
Please describe the problem: When the window to be vertically-maximized is touching the right edge of screen, using the maximize vertically shortcut maximizes the window completely. Using then the unmaximize option brings the window to the desired vertically maximized window. Using the shortcut when the window is not touching the right edge works fine. The bug is independent of the actual shortcut chosen for maximize vertically (tried both <control>-Up and <Shift><Control>-U) This bug was not present in previous version (2.8 and down) Steps to reproduce: 1. Select a window 2. Drag it so that the right edge touches the edge of the screen 3. Use maximize-vertically shortcut Actual results: The window maximizes completely Expected results: The window should maximize only vertically Does this happen every time? Yes Other information:
Caused by the patch in bug 163420 (though the original code was wrong too, so we just had a bug exchange). It took me a while to attempt to understand the logic of the 'if' statement in check_maximize_to_work_area(), so I put a huge comment in front of it stating what I think it is meant to do. I'll attach the patch in a minute and it seems to work for me, but considering that this code has been messed up a few times before, I'd appreciate some close scrutiny. :-) (Also, I think bug 167251 is a duplicate, but I'm not sure...)
Created attachment 45753 [details] [review] Attempt to fix vertical maximization acting as complete maximization
Havoc: ping. (It's been reported that this patch fixes bug 167251 as well...)
*** Bug 167251 has been marked as a duplicate of this bug. ***
Comment on attachment 45753 [details] [review] Attempt to fix vertical maximization acting as complete maximization Looks right to me. I guess this never worked at all...
Committed. avitzour@princeton.edu: Thanks for the level of detail in this bug; it was because of that detail that I was able to easily duplicate and then track down. ;-)
*** Bug 308292 has been marked as a duplicate of this bug. ***