Modal Windows"
m (remove empty version history (via JWB)) |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 11: | Line 11: | ||
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. | ||
| + | |||
| + | == Migrate Your Code from Event Thread == | ||
| + | |||
| + | With the Event thread, you might write your business logic right after <code>doModal()</code>. | ||
| + | <source lang="java" > | ||
| + | win.doModal(); | ||
| + | doMyTask(); //your business logic, need to move it for a servlet thread | ||
| + | </source> | ||
| + | |||
| + | Since now servlet thread doesn't stop at <code>doModal()</code>, you need to move your code to another place. You can put it at: | ||
| + | |||
| + | * Window's <code>onClose</code> event listener | ||
| + | * add a button in the modal window and call <code>doMyTask()</code> in an <code>onClick</code> listener and close the modal window. | ||
= Modal Windows with Event Thread = | = Modal Windows with Event Thread = | ||
| Line 18: | Line 31: | ||
When the event thread is suspended, the Servlet thread will be resumed and continue to loork 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 loork 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). | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
{{ZKDevelopersReferencePageFooter}} | {{ZKDevelopersReferencePageFooter}} | ||
Latest revision as of 05:54, 6 February 2024
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.
Migrate Your Code from Event Thread
With the Event thread, you might write your business logic right after doModal().
win.doModal();
doMyTask(); //your business logic, need to move it for a servlet thread
Since now servlet thread doesn't stop at doModal(), you need to move your code to another place. You can put it at:
- Window's
onCloseevent listener - add a button in the modal window and call
doMyTask()in anonClicklistener and close 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 loork 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).