Modal Windows"
m |
|||
| Line 1: | Line 1: | ||
| − | {{ | + | {{ZKDevelopersReferenceGuidePageHeader}} |
| − | + | = 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 (<javadoc method="doHighlighted()">org.zkoss.zul.Window</javadoc>). 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. | 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 (<javadoc method="doHighlighted()">org.zkoss.zul.Window</javadoc>). 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. | ||
| Line 12: | Line 12: | ||
The "next" message will be printed to the console before the end user closes the modal window. | 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, <javdoc method="doModal">org.zkoss.zul.Window</javadoc> will suspend the current thread. Thus, the "next" message won't be shown, until the modal window is closed. | If the event thread is enabled, <javdoc method="doModal">org.zkoss.zul.Window</javadoc> will suspend the current thread. Thus, the "next" message won't be shown, until the modal window is closed. | ||
| Line 18: | Line 18: | ||
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). | 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 : {{REVISIONYEAR}}/{{REVISIONMONTH}}/{{REVISIONDAY}} | ||
| + | {| border='1px' | width="100%" | ||
| + | ! Version !! Date !! Content | ||
| + | |- | ||
| + | | | ||
| + | | | ||
| + | | | ||
| + | |} | ||
| + | |||
| + | {{ZKDevelopersReferencePageFooter}} | ||
Revision as of 04:56, 15 November 2010
Template:ZKDevelopersReferenceGuidePageHeader
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
System.out.println("next");
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, <javdoc method="doModal">org.zkoss.zul.Window</javadoc> 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/11/15
| Version | Date | Content |
|---|---|---|