GNOME Bugzilla – Bug 373652
[KB-Fixed] Does not remember the left hand pane settings
Last modified: 2009-08-30 05:52:59 UTC
Forwarding this feature request from a downstream bug report: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210805 Description of problem: I have the panels under Evolution set up in a particular way (see the before pic attached to this BZ). If I minimize and then unminimize, the settings are not returned to the way they were prior to the minimize. Version-Release number of selected component (if applicable): 2.8.0-7.fc6 How reproducible: Always Steps to Reproduce: 1. Set up the panes (before.png) 2. Minimize so that the window is still on screen 3. Unminimize (after.png) Actual results: See the attached screenshots Expected results: before.png should be restored Additional info: This is an annoyance rather than a bug ;-) Screenshot (before.png): http://bugzilla.redhat.com/bugzilla/attachment.cgi?id=138525 Screenshot (after.png): http://bugzilla.redhat.com/bugzilla/attachment.cgi?id=138526
I can't reproduce then when going from maximized to minimized back to maximized, but if I switch from maximized to un-maximized (toggle the maximized state) it will sometimes shrink my left panel if the un-maximized window is too small to show the *right* panel. This seems to happen because the right panel has a minimum size requirement which is enforced to the left panel's detriment. Is this what you are seeing or am I seeing a different bug? I think a fix for this would be to separately store the left panel width for maximized and unmaximized states. This is also a problem in multi-monitor setups when moving a window from one screen to another. Moving a window un-maximizes, then potentially resizes the left panel, then re-maximizes, leaving you with a window that doesn't look the same as before you started moving it.
Panes are resizing and restoring correctly now on the kill-bonobo branch.
The "kill-bonobo" branch has been merged into "master" and will debut as Evolution 2.29.1. We believe the branch has addressed the reported issue. If you find the issue still exists in version 2.29 or later please feel free to re-open this bug. Closing as FIXED.