:19 PM UTC+3, vitrums wrote:
>
> [ Original post on StackOverflow
> http://stackoverflow.com/questions/40130383/howto-use-gwt-evenbus-to-schedule-openevent-closeevent-sequence
> ]
>
> Say we have few handlers for both events. The goal is to make sure, that
> all *OpenEvent ha
:
>
> [ Original post on StackOverflow
> http://stackoverflow.com/questions/40130383/howto-use-gwt-evenbus-to-schedule-openevent-closeevent-sequence
>
> ]
>
> Say we have few handlers for both events. The goal is to make sure, that
> all *OpenEvent handlers*finish before any of *Cl
Given that JS is single threaded using Scheduler.scheduleDeferred is your
only option. You could write your own EventBus implementation that might
use Scheduler.scheduleDeferred internally so that an event, fired during
another event being processed, gets delayed to the next browser event loop.
eduleDeferred(()
->wrapped.fireEventFromSource(event, source));
}
}
On 10/26/2016 12:51 PM, vitrums wrote:
[ Original post on
StackOverflow http://stackoverflow.com/questions/40130383/howto-use-gwt-evenbus-to-schedule-openevent-clo
[ Original post on
StackOverflow
http://stackoverflow.com/questions/40130383/howto-use-gwt-evenbus-to-schedule-openevent-closeevent-sequence
]
Say we have few handlers for both events. The goal is to make sure, that
all *OpenEvent handlers*finish before any of *CloseEvent handlers* start
