-
Enhancement
-
Resolution: Fixed
-
P4
-
1.4.1_05
-
b38
-
sparc
-
solaris
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.
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.
- relates to
-
JDK-4080029 Modal Dialog block input to all frame windows not just its parent.
-
- Resolved
-
-
JDK-4866704 JavaHelp Windows interaction with modal dialogs
-
- Resolved
-