GNOME Bugzilla – Bug 597094
Empty image window doesn't keep maximised state
Last modified: 2013-03-13 00:18:35 UTC
Steps to Reproduce: 1. Start GIMP 2. Maximise empty image window 3. Open an image 4. Edit (or not) an image 5. Save 6. Close image window Actual Results: Empty image window is no longer maximised. This bug also affects GIMP 2.6.7.(I don't know how to select two affected version in Bugzilla) There was different bug in 2.6.6 somehow related to this one: https://bugzilla.gnome.org/show_bug.cgi?id=563029. Maybe fix for that bug introduced this behaviour.
That is correct behavior according to the specification at http://gui.gimp.org/index.php/No_image_open_specification#closing_the_last_image
Notice, please, that I change "empty image window" first. So, according to the specification, it is my "user-override size/position" http://gui.gimp.org/index.php/No_image_open_specification#starting_with_no_image Then I open an image for editing and when I close it, image window should morph to "empty image window" size, which, in this case, is maximised window. I understand that in situation when I start GIMP, open image and then maximise window it would not be a bug. Last conversation about this problem with Peter Sikking on IRC, seams to confirm that it is, actually, a bug.
GIMP is not following the spec, reopening.
Let's aim for 2.6
*** Bug 599152 has been marked as a duplicate of this bug. ***
*** Bug 608485 has been marked as a duplicate of this bug. ***
*** Bug 646104 has been marked as a duplicate of this bug. ***
@Michal, a workaround for KDE -- define special settings for window (GIMP) and set "Maximized horizontally/vertically" to Force. I prefer having maximized window all the time than chasing Gimp window over the screen. Anyway, the bug lies somewhere else -- program should NOT hack Window Manager. It is WM task to set the window position and size, period. Once one tries to reinvent the wheel falls into trap of "fixing" hacking -- Window Manager, Session Manager, and so on. The more complex WM, the more complex "fixing" is. And 18 months of fixing such issue rather proves the "design" is broken.
2.6 -> 2.10
This got fixed with this commit: commit f45349e74cd7d9f6585613f9ec1e996d342dd407 Author: Michael Henning <mikehenning@eclipse.net> Date: Tue Apr 3 20:59:37 2012 -0400 app: Save the maximized state of the main window in the sessionrc file. (cherry picked from commit 89760cf044a9aed9b05dfb3f9e6d1da8449018d2) This is technically a new feature because it adds new stuff to sessionrc, but on the other hand not handling maximized state in sessionrc is worse, therefore merged to 2.8.
*** Bug 688080 has been marked as a duplicate of this bug. ***
Forgot to close.
*** Bug 690968 has been marked as a duplicate of this bug. ***