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 91023 - Modal window under an other window
Modal window under an other window
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Widget: Other
2.0.x
Other All
: Normal enhancement
: Small feature
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 340166
 
 
Reported: 2002-08-17 12:29 UTC by Victor Porton
Modified: 2014-03-22 22:06 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Victor Porton 2002-08-17 12:29:13 UTC 
Suppose that A is the main application window, B is a non-modal dialog
transient for A (e.g. a find dialog), and we call modal dialog C
(transient for A).

Now we can bring (by a mouse click) B above C what is wrong (as B does not
work because C is modal).

Two possible solutions are:

1. Leave GTK as is and let the programmer will manually set C transient
for B. It isn't good as is error-prone (easily to forget) and a programmer
should add setting transiency for every new non-modal dialog.

2. When we run a modal dialog C, which is transient for a window A,
automatically make it also transient for every window which is transient
for A (except from C itself). It seems to be a good solution and will most
probably break no existing code compatibility.
Comment 1 Havoc Pennington 2002-08-17 14:21:39 UTC 
You can only set one transient parent though.
Comment 2 Owen Taylor 2002-09-20 21:41:59 UTC 
MWM, I believe had an "Application modal" flag as well as
a "System modal" flag that could be put on a dialog - 
I suppose we could get something like this added to the
NET WM spec and have GTK+ set it on the modal dialog
that currently has the active GTK+ grab.

Then the window manager could be smarter about stacking
order.

I don't think this problem is solveable in GTK+ alone.

This should be brought up on wm-spec-list@gnome.org
Comment 3 Havoc Pennington 2002-09-20 22:21:54 UTC 
There is already a MODAL state hint in the WM spec - I think it's
intended to be application modal. I don't think we have a hint for
system modal, other than the old Motif one.
Comment 4 Owen Taylor 2002-09-20 23:14:59 UTC 
Cool, then we just need to implement the 
set-modal-on-current-modal-dialog feature, and then I
can reassign this bug to metacity :-)
Comment 5 Matthias Clasen 2014-03-22 22:06:34 UTC 
closing out old bugs