import"RTC.idl";
Detailed Description
Member Function Documentation
◆ attach_context()
|
inherited |
attach_context
Description
Inform this RTC that it is participating in the given execution context. Return a handle that represents the association of this RTC with the context.
Semantics
This operation is intended to be invoked by ExecutionContextOperations::add_component (see Section 5.2.2.6.6). It is not intended for use by other clients.
◆ detach_context()
|
inherited |
detach_context
◆ exit()
|
inherited |
exit
Description
Stop the RTC’s execution context(s) and finalize it along with its contents.
Semantics
Any execution contexts for which the RTC is the owner shall be stopped. If the RTC participates in any execution contexts belonging to another RTC that contains it, directly or indirectly (i.e., the containing RTC is the owner of the ExecutionContext), it shall be deactivated in those contexts. After the RTC is no longer Active in any Running execution context, it and any RTCs contained transitively within it shall be finalized.
Constraints
An RTC cannot be exited if it has not yet been initialized. Any attempt to exit an RTC that is in the Created state shall fail with ReturnCode_t::PRECONDITION_NOT_MET.
◆ finalize()
|
inherited |
finalize
Description
Finalize the RTC that realizes this interface, preparing it for destruction.
Semantics
This invocation of this operation shall result in the invocation of the callback ComponentAction::on_finalize
Constraints
- An RTC may not be finalized while it is participating in any execution context. It must first be removed with ExecutionContextOperations::remove_component. Otherwise, this operation shall fail with ReturnCode_t::PRECONDITION_NOT_MET. See Figure 5.9.
- An RTC may not be finalized while it is in the Created state. Any attempt to invoke this operation while in that state shall fail with ReturnCode_t::PRECONDITION_NOT_MET.
- Application developers are not expected to call this operation directly; it exists for use by the RTC infrastructure.
◆ get_context()
|
inherited |
◆ get_context_handle()
|
inherited |
◆ get_owned_contexts()
|
inherited |
get_owned_contexts
Description
This operation returns a list of all execution contexts owned by this RTC.
◆ get_participating_contexts()
|
inherited |
- get_participating_contexts
Description
This operation returns a list of all execution contexts in which this RTC participates.
Semantics
Each call to attach_context causes the provided context to be added to this list. Each call to detach_context causes the provided context to be removed from this list.
◆ initialize()
|
inherited |
initialize
Description
Initialize the RTC that realizes this interface.
Semantics
The invocation of this operation shall result in the invocation of the callback ComponentAction::on_initialize.
Constraints
◆ is_alive()
|
inherited |
is_alive
Description
A component is alive or not regardless of the execution context from which it is observed. However, whether or not it is Active, Inactive, or in Error is dependent on the execution context(s) (see Figure 5.7) in which it is running. That is, it may be Active in one context but Inactive in another. Therefore, this operation shall report whether this RTC is either Active, Inactive, or in Error; which of those states a component is in with respect to a particular context may be queried from the context itself.
◆ on_aborting()
|
inherited |
◆ on_action()
|
inherited |
on_action
Description
The indicated FSM participant RTC has been invoked as a result of a transition, state entry, or state exit in its containing FSM.
Constraints
- The given execution context shall be of kind EVENT_DRIVEN.
◆ on_activated()
|
inherited |
◆ on_deactivated()
|
inherited |
◆ on_error()
|
inherited |
on_error
Description
The RTC remains in the Error state.
Semantics
If the RTC is in the Error state relative to some execution context when it would otherwise be invoked from that context (according to the context’s ExecutionKind), this callback shall be invoked instead. For example,
- If the ExecutionKind is PERIODIC, this operation shall be invoked in sorted order at the rate of the context instead of DataFlowComponentAction::on_execute and on_state_update.
- If the ExecutionKind is EVENT_DRIVEN, this operation shall be invoked whenever FsmParticipantAction::on_action would otherwise have been invoked.
◆ on_finalize()
|
inherited |
on_finalize
Description
The RTC is being destroyed.
Semantics
Any final RTC-specific tear-down logic should be performed here.
◆ on_initialize()
|
inherited |
on_initialize
Description
The RTC has been initialized and entered the Alive state.
Semantics
Any RTC-specific initialization logic should be performed here.
◆ on_reset()
|
inherited |
on_reset
Description
The RTC is in the Error state. An attempt is being made to recover it such that it can return to the Inactive state.
Semantics
If the RTC was successfully recovered and can safely return to the Inactive state, this method shall complete with ReturnCode_t::OK. Any other result shall indicate that the RTC should remain in the Error state.
◆ on_shutdown()
|
inherited |
on_shutdown
Description
The given execution context, in which the RTC is participating, has transitioned from Running to Stopped.
◆ on_startup()
|
inherited |
on_startup
Description
The given execution context, in which the RTC is participating, has transitioned from Stopped to Running.
The documentation for this interface was generated from the following file:
- idl/RTC.idl
