From Documentation

(Difference between revisions)
Jump to: navigation, search
m (Modal Windows with Event Thread)
Line 19: Line 19:
=Version History=
=Version History=
{| border='1px' | width="100%"
{| border='1px' | width="100%"
! Version !! Date !! Content
! Version !! Date !! Content

Revision as of 07:56, 17 December 2010

Modal Windows with Servlet Thread

When the event is processed in the Servlet thread (default), the execution cannot be suspended. Thus, the modal window behaves the same as the highlited window (Window.doHighlighted()). At the client side, the visual effect is the same: a semi-transparent mask blocks the end user from access components other than the modal window. However, at the server side, it works just like the overlapped mode – it returns immediately without waiting for user's closing the window.

 win.doModal(); //returns once the mode is changed; not suspended

The "next" message will be printed to the console before the end user closes the modal window.

Modal Windows with Event Thread

If the event thread is enabled, Window.doModal() will suspend the current thread. Thus, the "next" message won't be shown, until the modal window is closed.

When the event thread is suspended, the Servlet thread will be resumed and continue to fork another event thread to process other events, if any. Thus, the end user still have the control (such that he can close the modal window if he want).

Version History

Last Update : 2010/12/17

Version Date Content

Copyright © Potix Corporation. This article is licensed under GNU Free Documentation License.