we have just discovered this NOTE in the description of the Launch
action:
--- NOTE - Any events that are generated during the execution of these
--- steps are queued and dealt with only after the entire sequence has
--- ended.
The steps refered to are the three activities performed to launch the
new application.
I am wondering what this means, and what the implications are. It
relates somehow to the meaning of "synchronous" events (i.e. immediate
execution of actions) and "asynchrounous" events (queueing of events).
Does it mean that the synchronous events such as "IsStopped" are handled
asynchrounous? Since asynchronous events are flushed when changing the
scope (along with the actions still in the queue) a clarificaion is
required.
The note might aim at the implications of events which are generated
during the destruction of Group classes. It is simply a difficult
situation when a link is triggered to perform a Launch during the
execution of another Launch. Perhaps the clarification should be "all
links are disabled during execution of the transistion/launch"?
You might now that there is the Australia meeting coming up soon. I'd
like to ask the active developers to contribute to the meeting by
indicating questionable parts of the standard. We have to setup a
maintainance task force to deal with these issues.
- Klaus
-- GMD FOKUS German National Research Center for Information Technology Klaus Hofrichter Kaiserin-Augusta-Allee 31 D-10589 Berlin Germany mailto:hofrichter@fokus.gmd.de http://www.fokus.gmd.de/usr/hofrichter P: +49 30 3463 7211 Fx -8211 There is a reexamination, but no reparty