Red Hat Bugzilla – Bug 1031106
Left dock toolbox shrinks horizontally when attached panel to another column
Last modified: 2016-10-14 06:29:35 EDT
+++ This bug was initially created as a clone of Bug #916604 +++
Description of problem:
The Gimp 2.8 has a new feature to attach the toolbar into several columns. When I attached Tool option panel (in default under the Toolbox) to the right side of the Toolbox (the toolbox and tool options are now horizontally, not vertically as before), the toolbox shrinks into one column of tool icons and expand horizontally behind the monitor borders. It's especially annoying in single window mode, when in does not permit the fullsreen mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Start gimp
2. Enable single-window mode (Windows -> Single-Window mode)
3. Drag&drop the Tool options (by default under the Toolbox) from its original position right side of the Toolbox
4. Try to maximize of F11 to fullscreen
The Toolbox shrinks and you are unable to resize the gimp vertically. The fullscreen does not work at all and behaves weird
The gimp should now the maximal height of the monitor and if the shrunk toolbox does fit the height, it should expand a bit to the width.
--- Additional comment from Nils Philippsen on 2013-11-15 10:43:32 EST ---
The reason for this is that moving the tool options dockable to the right "squeezes" the toolbox so it's only one column wide, but very tall (too tall for most displays), which results in e.g. GNOME Shell refusing to "maximize" the window, i.e. fit it into the current display, which it can't because the window is already taller than the display.
Here's a workaround: After step 3, there's a handle to the right side of the tool options dockable. Drag it to the right, creating some space for the toolbar so it can use additional columns. Then you should be able to reduce the window height, or maximize it.
I'll clone this for Fedora, and raise this with upstream -- I'm not familiar with the UI layout code and can't estimate how much effort it would be to fix this.
Adding FutureFeature so this bug isn't closed automatically.
I don't see how I could fix this and it's reported upstream, closing.