Bug ID: JDK-4129665 Opening modal dialogs blocks the program stack

Type: Bug
Component: client-libs
Sub-Component: java.awt
Affected Version: 1.0.2,1.2.0,1.3.0

Priority: P4
Status: Closed
Resolution: Duplicate
OS: solaris_2.3,solaris_2.5,windows_nt
CPU: generic,x86

Submitted: 1998-04-16
Updated: 2001-11-16
Resolved: 2001-11-16


Name: rk38400			Date: 04/16/98


It appears that the concept of modality of the user interface has gotten tied directly to the blocking of the program stack.
Just because I want to prevent the user from interacting with other windows while a modal dialog is open,
it does not imply I want to block my program stack. I will give you that there are times where I might want to do both,
but not all the time.

Are the modality of the UI and the blocking of the program stack considered a feature or a bug. I certainly consider it a bug.
(Review ID: 28234)
======================================================================

EVALUATION I agree that it would also be nice to have the option of getting a modal dialog where the calling thread does not block on the call to show(). Since it's *also* useful to have the blocking version for convenience, I do not consider this a bug, but more of a Request for Enhancement to add the non-blocking API. We could either do this in Swing by using the glasspane to implement modality, or we could get this implemented in the AWT. amy.fowler@Eng 1998-05-29 This bug appears to be a duplicate of 4178473 "Dialogs needs modality which blocks input only to owner window" tim.bell@Eng 1999-06-24 Duplicate of 4080029 ###@###.### 2001-11-16

24-06-1999

Duplicate :	JDK-4080029 - Modal Dialog block input to all frame windows not just its parent.
Duplicate :	JDK-4303274 - Dialog class should support a modal dialog that is non blocking
Relates :	JDK-4178473 - Dialogs needs modality which blocks input only to owner window