"Application-modal. An application-modal dialog box blocks all windows from the same application,
except for those from its child hierarchy. If several
applets are launched in a browser environment, the browser is allowed to treat them either as separate applications or as a single application. The behavior is implementation-dependent."
Would an application-modal be appropriate for an application that requires the user to confirm before doing anything?
Is the attached, which is only being attached for educational purposes, an illustration of the child hierarchy mentioned? Is it complete?
Why do you think it is useful to allow objects in the child hierarchy not to be blocked?
Is there some overriding method() which allows me to switch modes, or would I have to design the application in
modeless mode? This is because it is not always the case that I can predict all possible user scenarios, although I do my best to do so
Toolkit-modal. A toolkit-modal dialog box blocks all windows that run in the same toolkit, except those from its child hierarchy. If several applets are launched, all of them run with the same toolkit. Hence, a toolkit-modal dialog box shown from an applet may affect other applets and all windows of the browser instance that embeds the
Java runtime environment for this toolkit."
Can you clarify and illustrate with a working example? Is the author referring to particular classes, such as java.awt.Toolkit?
Sourced from
here.