GNOME Bugzilla – Bug 124633
does not save maximized window state
Last modified: 2004-12-22 21:47:04 UTC
Not sure if this is a bug in pan or gnome-*, but pan does not appear to save the maximized state of it's window after a clean exit. To duplicate: 1. open pan, note it's in a non-maximized state (for me anyway) 2. file->exit to ensure you are exiting cleanly 3. restart pan and note that it is back to having the same position and non-maximized state What should happen: Pan should save it's window size, position and maximized/non-maximized state on exit, and attempt to return to the previous state when it is re-started again. I attempted to remove the geometry keys from the ~/.pan/config.xml file and then restart pan (it started with the default position), maximize, exit and restart and it returned back to it's former un-maximized state. The non-maximized state I have to add, is *almost* maximized, with the left and bottom of the window flush with the left and bottom of the screen/gnome-panels, but the top of the window about 2 pixels too low and the right of the window about 5 pixels too far to the right. Incidently I have a dual monitor setup with xinerama through the nvidia dual screen sextion of the driver, which may be causing the strangeness. Maybe Pan can't handle being maximized on one of two screens?
this happens on a single monitor system too. Fedora Core 1, Pan 0.14.2
Confirmed. This is because of this line in util.c::gui_save_window_size(): if (window->maximize_initially) { g_snprintf (buf, sizeof(buf), "/Pan/Geometry/%s_max", key); pan_config_set_bool (buf, TRUE); } gtk doesn't set GtkWindow.maximize_initially when a window is maximized.
Fixed in CVS: http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan&command=DIFF_FRAMESET&file=ChangeLog&rev1=1.2020&rev2=1.2021&root=/cvs/gnome http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan/pan&command=DIFF_FRAMESET&file=util.c&rev1=1.250&rev2=1.251&root=/cvs/gnome