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 316521 - Layer color adjustment dialogs do not display on foreground
Layer color adjustment dialogs do not display on foreground
Status: RESOLVED NOTGNOME
Product: GIMP
Classification: Other
Component: User Interface
2.3.x
Other Linux
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 317167 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-09-16 20:58 UTC by che
Modified: 2008-01-15 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description che 2005-09-16 20:58:24 UTC 
Version details: build from source
Distribution/Version: Gentoo

If I choose a layer color adjustment from the image menu (on the right click:
layer/colors/curves -- for example), the following dialog displays on the
background instead of jumping up to the front. That is kind of confusing, since
the behavior I'd expect after selecting menu item for curves would be to have
the dialog on foreground and let me do my adjustments, instead of looking for it
in the taskbar.

Other dialogs, such as "Save as..." and effects behave normally.
Comment 1 Sven Neumann 2005-09-16 21:39:45 UTC 
GIMP cannot control where your window manager puts the dialog. If it puts new
windows below already mapped ones, I would consider that a bug in your WM and
suggest that you file a bug report against it.

The only thing gimp can do is to make the dialog transient to the image window.
We tried that but it caused bug #128833. In the current development version we
are again making more use of transient relationships. So it seems to make sense
to treat at least the color correction tool dialogs like plug-in dialog and set
them transient. I have done that change in CVS now. Let's see how it turns out...
Comment 2 che 2005-09-17 02:44:38 UTC 
That fixes it for me, thanks for such a quick reaction!
Comment 3 Michael Natterer 2005-09-25 17:52:47 UTC 
*** Bug 317167 has been marked as a duplicate of this bug. ***