Thanks for the explanation. Makes sense.
Easier to understand for RPC, a bit harder to get for UI events.
On Sep 1, 8:56 am, Jason Morris [EMAIL PROTECTED] wrote:
This is the way it's done.
You can think of JavaScript as running on the event-dispatch-thread.
Therefore, opening a DialogBox
Iama, under what conditions do you need to use callbacks? Can you give an
example?
Also, to gwt-user: you may get mouse-down/mouse-up events (which is wrong,
but just changes the appearance of a button, or sets focus) but I don't
think you can do anything with them (like enter text, or click).
I have the same question.
I've had to workaround this by adding callbacks to transfer the data
from the dialog back to the caller.
Regards,
lama
On Aug 29, 9:16 am, gwt-user [EMAIL PROTECTED] wrote:
1. To illustrate the first point. In the following code:
boolean ok = Window.confirm(Are
This is the way it's done.
You can think of JavaScript as running on the event-dispatch-thread.
Therefore, opening a DialogBox and making the thread wait until a button is
clicked results in the following on the queue:
++ +-+
| wait for click | - | click event
1. To illustrate the first point. In the following code:
boolean ok = Window.confirm(Are you sure .);
if (ok) {
}
code inside the if block will be executed only after user presses
button on the confirm dialog. Is it possible to do the same with
instance of DialogBox?
2.
