GNOME Bugzilla – Bug 57952
no scrollable scroll bars in new picture from a selection
Last modified: 2009-08-15 18:40:50 UTC
With version 1.2.0 and 1.2.2pre3 I got the following little problem. 0. The Preferences for resizing a window by zoom function are switched off. 1. I select a small part of my pic with the square selector 2. Copy it with Ctrl-C 3. make a new picture with this selection (paste as new picture) 4. rescale it with the picture scaling function The new picture will be rescaled, but the window size hasn't changed (as expected). But the scroll bars don't let me scroll the picture. They are there but show that the picture is only as big as the window size. If then .. 5. I resize my window a little bit ... then I can scroll the new (big) picture. Tried with different values of rescaling amounts. If my preferences let the window resize by zooming, than everything seems to be OK. Any suggestions? norbert
I can reproduce it with 1.2.2 (final release) under Solaris. I can add some more details: - While resizing the image, I could see a larger window allocated for a fraction of a second, but then it came back to its original size immediately afterwards, and the scrollbars were unusable as you described. - Using "<Image>->View->Shrink Wrap" has no effect initially: the window remains at its original size (too small, unusable scrollbars). But if I resize the window, the scrollbars appear and afterwards it is possible to use "Shrink Wrap" and to get the expected effect. This may be related to bug #22567 and bug #13296, although I doubt that it is a window manager issue in this case, since the window should not be resized when the image is resized (according to the preferences) so the window manager should not be involved. However, the fact that I saw a larger window flashing on my screen for a few milliseconds makes me think that there are some strange things happening somewhere in the GIMP, GTK+ or both. By the way, I tested this with gtk+-1.2.10.
reproduced problem with 1.2.2
We should have a look at this before 1.2.4.
I can still reproduce the problem with pre-1.2.4.
Suggest bumping it to 1.2.5 Dave.
I marked this bug as depending of bug #22567 because the fix for both is the same. Whatever the resolution is for #22567 it's also the same for this one. #22567 has been suggested as WONTFIX, so postponing this one to 1.2.5 is not a good idea. Maybe marking it as a duplicate of 22567 is a better approach.
*** This bug has been marked as a duplicate of 22567 ***