Re: Concurrent Schedules

[Vladimir Jojic]

Doug,

Thanks for pointing this out. Problem was the way Randomized execution
order in Schedule was implemented: ConcurrentGroups would inherit default
order from schedules in which they are created. This way user did not have
to go through customization of ConcurrentGroup and then setting the type
of the concurrent group in Schedule, instead they would just call
setDefaultOrder on the Schedule. 

In turn this approach prevented user from setting their own customized
concurrent groups as concurrent group types in schedules (like you tried
with concurrent schedule) ...

This is fixed now and in fact it is required that users create customized
ConcurrentGroups that have Randomized execution order and set them as
Concurrent Group type in Schedules in which that they want to have
concurrent actions performed in random order. 

Regards,
Vladimir

PS. The empty schedule problem that Geoffrey pointed out is also fixed.
Thanks Geoffrey!


                  ==================================
   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.