Re: ordering events in a swarm ....

[Marcus G. Daniels]

>>>>> "XH" == xueyue  <address@hidden> writes:

XH> this will work, but a new problem arise: the
XH> actions inserted after [[schedule activateIn: nil] run] will start
XH> to be excuted only if those before [[schedule activateIn: nil]
XH> run] has been completed. 

Apparently we're using a different implicit definition of "work".
(This is the intended behavior.)

What is your goal?  

One example of where this usage might be useful is if you wanted to
re-run an experiment with a few added perturbation events.  Of course,
to do this would probably mean reloading or recreating agent state
(e.g. -buildObjects).

If you want the ever-evolving dynamic schedule, with no history,
use the same schedule instance within the same activateIn:/run context.


                  ==================================
   Swarm-Support is for discussion of the technical details of the day
   to day usage of Swarm.  For list administration needs (esp.
   [un]subscribing), please send a message to <address@hidden>
   with "help" in the body of the message.