After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 692847 - Bottom layer blocked by Windows 7 taskbar (many layer image)
Bottom layer blocked by Windows 7 taskbar (many layer image)
Status: RESOLVED DUPLICATE of bug 686860
Product: GIMP
Classification: Other
Component: User Interface
2.8.2
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-01-29 23:47 UTC by Moltres_rider
Modified: 2013-01-30 22:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Moltres_rider 2013-01-29 23:47:39 UTC 
If I start adding many layers to an image in Windows 7 that it fills up the layer window, and I drag the layers tab up to the top of the screen, Windows 7 auto maximize window mechanism kicks in and the bottom layer in the layers window is inaccessible (it is under the taskbar)... due to Windows 7's drag to top to maximize feature, it is not possible to drag the layers window to the top of the screen where I can work on the bottom layer without windows autoresizing the layers window hence putting the bottom layer under the taskbar (where I cannot get to it)... this needs to be corrected because Windows 7 features are making it impossible to access the bottom layer in Gimp
Comment 1 Michael Schumacher 2013-01-30 00:04:56 UTC 
Do you know how an application may prevent this?
Comment 2 Moltres_rider 2013-01-30 00:16:29 UTC 
I don't get what you are asking...
Comment 3 Max Mustermann 2013-01-30 21:58:26 UTC 
As a workaround you can set the Layers tab back to normal size (e.g. move the tab window away from the screen top) and then resize it. 
The multi-window mode is known to ignore the screen height. Is the described behavior a duplicate of bug #686860? If yes, please mark it so. Thank you in advance.
Comment 4 Moltres_rider 2013-01-30 22:59:48 UTC 
eeyup...

*** This bug has been marked as a duplicate of bug 686860 ***