JDK-4813288 : Need a way to exempt some windows from disablement when a modal dialog is shown
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 1.4.1_05
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris
  • CPU: sparc
  • Submitted: 2003-02-05
  • Updated: 2005-05-21
  • Resolved: 2005-05-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 6
6 b38Fixed
Related Reports
Relates :  
JDK-4866704 - JavaHelp Windows interaction with modal dialogs
Relates :  
JDK-4080029 - Modal Dialog block input to all frame windows not just its parent.
Description
In SunONE Studio/NetBeans, there are some serious problems in the relationship
between the Help window and modal dialogs.  We are using JavaHelp, and the help
window is a Swing component in the same JVM as the rest of the application.

The problem is this:  When a modal dialog is shown, the Help window is frozen.
Yet it is not uncommon for users to either want to browse the help to learn
how to complete the dialog;  also, invoking help from within a dialog is not
uncommon.

We currently use a workaround with some bad side effects;  however, it must be
true that anyone utilizing JavaHelp has this same problem.  A clean solution 
would allow specific windows to specify (probably via client properties) that
they are not to be disabled when a modal dialog is shown.
Comments
WORK AROUND 1. Whenever a modal dialog is opened, reparent the help component into a dialog owned by the modal dialog. This has embarrassing side effects, such as the help being fronted and its window size changed whenever a modal dialog is invoked. 2. Run the help system in a separate JVM (this is not desirable for performance reasons) 3. Invoke no modal dialogs in the system, and instead make dialogs appear modal by disabling all other windows in the system temporarily (this is not really possible in a modular environment such as NetBeans/S1S - there is no guarantee that all modules a user has installed will comply with a directive never to use modal dialogs)
14-08-2004
SUGGESTED FIX Allow some means of flagging windows which should not ever be disabled because a modal dialog is present. I'd suggest something like putClientProperty ("exemptFromModality") or something such.
14-08-2004
PUBLIC COMMENTS In SunONE Studio/NetBeans, there are some serious problems in the relationship between the Help window and modal dialogs. We are using JavaHelp, and the help window is a Swing component in the same JVM as the rest of the application. The problem is this: When a modal dialog is shown, the Help window is frozen. Yet it is not uncommon for users to either want to browse the help to learn how to complete the dialog; also, invoking help from within a dialog is not uncommon. We currently use a workaround with some bad side effects; however, it must be true that anyone utilizing JavaHelp has this same problem. A clean solution would allow specific windows to specify (probably via client properties) that they are not to be disabled when a modal dialog is shown.
14-08-2004
EVALUATION Related to 4080029. ###@###.### 2003-02-05 Name: osR10079 Date: 02/06/2003 We should consider this kind of modality when we work on 4080029. ###@###.### 2003-02-06 ====================================================================== Implemented as a part of 4080029. ###@###.### 2005-05-04 12:06:45 GMT
06-02-2003