Class Statechart<T extends Enum<T> & IStatechartState<?,T>>

public class Statechart<T extends Enum<T> & IStatechartState<?,T>>
extends Object
implements Serializable, com.anylogic.engine.internal.Child

Statechart - the most advanced construct to describe event- and time-driven behavior. Statechart has states and transitions. Transitions may be triggered by timeouts or rates, messages received by the statechart, and conditions. Transition execution may lead to a state change where a new set of transitions becomes active. States in the statechart may be hierarchical, i.e. contain other states and transitions. The actual structure of state diagram is stored in the agent.
There are two ways to send a message to the statechart:
- call receiveMessage(Object) or receiveMessage(int) method, and
- call fireEvent(Object) method.
receiveMessage() assumes no queuing for incoming messages. If the received message cannot immediately cause scheduling of a transition, it is discarded. Therefore, if, for example, there are two transitions: one (from state S0 to S1) triggered by message A, and another (from S1 to S2) triggered by message B, and the statechart receives messages A and B at the same time while in the state S0, only first transition will be taken, and message B will be discarded.
fireEvent() supports queuing for incoming messages. The message added to the queue by fireEvent() can be consumed either immediately or after a number of zero-time steps of the statechart, otherwise it will be discarded. In the example above both transitions will be taken if the messages A and B are received via fireEvent() method.
Using fireEvent() is less efficient than using receiveMessage() both time and memory-wise, so if you do care and are sure that no "chains" of zero-time message-triggered transitions can happen, use receiveMessage().
Memory: sizeof(Object) + 18 bytes + sizeof(array with concurrently active transitions) + sizeof(message queue)