Shutting Down a JADE Session

JADE rejects Windows log-off or shut-down requests if a modal form or a Windows dialog (for example, a message box, a common dialog, and so on) is currently active, because in those cases, the calling method has been suspended until the dialog is closed.

The user must complete the required actions on that dialog before the suspended method logic can continue. Graceful shut down of the application can be accomplished only if the application is in a truly idle state.

If the JADE application does not have any suspended modal or dialog methods in progress, requesting a Windows log off or shut down is not rejected by the JADE application. JADE calls the queryUnload and unload methods on each form (in the correct order), and terminates gracefully.

If the JADE application has suspended modal or dialog methods in progress, requesting a Windows log off or shut down is rejected and the log off or shut down action will not occur. The user must complete or cancel the current modal dialog or dialogs and then request the log off or shut down action again.

The best policy for a user is to shut down all applications before requesting that Windows logs off or shuts down.