Orocos Real-Time Toolkit 2.6.0
A general compare condition. More...
|ConditionCompare (internal::DataSource< T > *data1, internal::DataSource< T > *data2)|
|virtual ConditionInterface *||clone () const|
|The Clone Software Pattern. |
|ConditionCompare *||copy (std::map< const base::DataSourceBase *, base::DataSourceBase * > &alreadyCloned) const|
|When copying an Orocos program, we want identical internal::DataSource's to be mapped to identical DataSources, in order for the program to work correctly. |
|Evaluate the Condition and return the outcome. |
|virtual void||reset ()|
|Some conditions need to be reset at some points. |
A general compare condition.
This compares two variables of type T, which it gets from two internal::DataSource<T>, using the compare_op given. You should use std::less, std::less_equal, std::greater, std::greater_equal, std::equal_to and std::not_equal_to or other binary predicate functors as compare_op.
|ConditionCompare* RTT::scripting::ConditionCompare< T, compare_op >::copy||(||std::map< const base::DataSourceBase *, base::DataSourceBase * > &||alreadyCloned||)|| const
This is different from the clone function, where we simply want a new Command that can replace the old one directly.
This function takes a map that maps the old internal::DataSource's onto their new replacements. This way, it is possible to check before cloning a internal::DataSource, whether it has already been copied, and if so, reuse the existing copy.
To keep old source working, the standard implementation of this function simply calls the clone function. If your ConditionInterface uses a internal::DataSource, it is important that you reimplement this function correctly though.
Reimplemented from RTT::scripting::ConditionInterface.
|bool RTT::scripting::ConditionCompare< T, compare_op >::evaluate||(||)||
Some conditions need to be reset at some points.
E.g. a scripting::ConditionDuration counts the time since the first time a Command was executed, and if this time exceeds a certain preset time, returns true. Therefore, it needs to be reset, i.e. it needs to start counting, when the command is first executed.. scripting::ConditionOnce has a similar need. This function is called at such times.
Reimplemented in RTT::scripting::ConditionBinaryCompositeAND, RTT::scripting::ConditionExpire, RTT::scripting::ConditionDSDuration, RTT::scripting::ConditionCache, RTT::scripting::ConditionDuration, RTT::scripting::ConditionBoolDataSource, and RTT::scripting::ConditionOnce.