schedule orders

[Nelson Minar]

this stuff is so complicated!

>> *** --> I am assuming that actions and action groups will get executed in
>> the order they are *activated*. Is this correct, Roger ?
>Yes, this is the uniform rule we established for all cases in which actions
>were scheduled at the same time step. 

OK, I can live with that. So I thought the trivial thing to be able to
display the initial condition was to do this in the ObserverSwarm

-activateIn: (id) swarmContext {
  [super activateIn: swarmContext];
  [displaySchedule activateIn: self];
  [modelSwarm activateIn: self];
  return [self getActivity];
}

but there's a hidden gotcha here. The display is now *behind* the
model in terms of time. That means that click-to-probe in a Raster
doesn't work right. Bummer.

It should be possible to click on a probe window to have it
automatically update itself to the exact value right now. Maybe just a
mouse binding to do
 [probeDisplayManager update];
As it stands now, probes *look* like they're reflecting the current
state of objects, but in fact they may or may not be..

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