c++_api/inc/opals/IControlObject.hpp
22 is set synchronous by the modules. Attention: complex code within that the member functions (especially \see setSteps)
23 will slow down the processing performance. If the object is also accessed from a second thread, its the objects
26 A control object can be passed (by reference) to a OPALS module either while creating a new instance or using the
27 opals::IModuleBase::set_controlObject. It's the programmers responsibility to secure proper lifetime of the control
30 To interrupt processing throw the opals::Exceptions::UserInterrupt within the overloaded member function (mainly relevant in setSteps).
37 /// sets the descriptions of the stages (implicitly sets the number of stages. it will be set within the module's run function)
41 /// In rare situations no step information will be available for a certain stage. Usually those stages are processed quite quickly
44 /// \brief sets the number of steps for the current stage (will be called after the stage was set)
