Not for direct use, provides the power behind both void signals and slots. More...
|typedef std::map< std::string, |
const Subscribers * >
|Stores publishing topics and their followers. |
|typedef Topic< Void >::Subscribers||Subscribers|
|A list of subscribers (slots) to a given topic. |
|void||connectSignal (const std::string &topic)|
|Connect a signal to the specified topic. |
|void||connectSlot (const std::string &topic)|
|Connect a slot to the specified topic. |
|Decrement the counter for the number of copies of this object. |
|void||disconnect (const std::string &topic)|
|Disconnect the sigslot from the specified topic. |
|Disconnect the sigslot from all topics. |
|Emit a signal. |
|const unsigned int &||handles () const|
|Number of copies of this object. |
|Increment the counter for the number of copies of this object. |
|void||process (Void void_arg=Void())|
|Process the callback function loaded into this sigslot. |
|SigSlot (VoidFunction f)|
|template<typename C >|
|SigSlot (void(C::*f)(void), C &c)|
|Disconnects the sigslot completely. |
|NullaryFunction< void > *||function|
|std::set< std::string >||subscriptions|
Not for direct use, provides the power behind both void signals and slots.
This is the workhorse for both signals and slots, providing the implementation for all the functions necessary by both types of frontends. This is the specialisation of the general case for void callbacks.
Disconnects the sigslot completely.
This is a rather elaborate process, it must first disconnect from any signals to ensure no new callbacks are instantiated, then check to see that there are no callbacks actually running, block if so, then finalise any deletions.