Statecharts

Programming complex behavior or event-dependent processes in ArmarX is done with Statecharts. For more details refer to ArmarX Statecharts. More...

Classes

class  DynamicRemoteState
 DynamicRemoteStates can be used to connect to remote statecharts dynamically at runtime. More...
 
class  FinalStateBase< EventType, StateType >
 
class  ParameterMapping
 This class maps parameters from several source dictionaries to one input dictionary. The mapping depends on an instance of ParameterMappingIceBase, in which the mapping is specified.
More...
 
class  RemoteState
 This Statetype is used to create a state instance that represents a state that is located in another application. It is added in a parent state by calling State::addRemoteState(statename, proxyname).
If a RemoteState is entered for the first time, it creates automatically a new instance at the remotely located RemoteStateOfferer that contains the real state. The RemoteState receives upon creation of the new real-state instance an unique id of this state for further communication.
This id is automatically used in the onBreak- and onExit-functions, to communicate with the correct state.
Except the state creation-call (which should return immediately) all remote procedure calls are async calls. More...
 
class  RemoteStateOfferer< ContextType >
 Class that holds states, which offer functionality for other states over Ice. More...
 
class  RemoteStateWrapper
 
class  State
 
class  StateBase
 
class  StatechartContext
 This class contains a statechart and provides the interfaces to distributed components. More...
 
class  StateController
 
class  StateTemplate
 
class  StateUtility
 

Modules

 XMLStateComponent
 

Typedefs

using CounterState = CounterStateTemplate< EvCounterNotFulfilled, EvCounterFulfilled >
 CounterState is a typedef for the CounterStateTemplate, that uses the events EvCounterNotFulfilled and EvCounterFulfilled. More...
 
using FailureState = FinalState< Failure >
 
using SuccessState = FinalState< Success >
 

Detailed Description

Programming complex behavior or event-dependent processes in ArmarX is done with Statecharts. For more details refer to ArmarX Statecharts.

Typedef Documentation

◆ CounterState

using CounterState = CounterStateTemplate<EvCounterNotFulfilled, EvCounterFulfilled>

#include <ArmarXCore/statechart/standardstates/CounterState.h>

CounterState is a typedef for the CounterStateTemplate, that uses the events EvCounterNotFulfilled and EvCounterFulfilled.

See also
CounterStateTemplate

Definition at line 97 of file CounterState.h.

◆ FailureState

#include <ArmarXCore/statechart/standardstates/FinalState.h>

State that automatically signals "Failure" to the parent state. See class FinalStateBase for more information.

Definition at line 184 of file FinalState.h.

◆ SuccessState

#include <ArmarXCore/statechart/standardstates/FinalState.h>

State that automatically signals "Success" to the parent state. See class FinalStateBase for more information.

Definition at line 173 of file FinalState.h.