NSCore::DataSetChainMember Class Reference
Consume datasets, do something with them and give them to the next consumer. More...
#include <datasetchain.h>
Public Member Functions | |
| DataSetChainMember (QObject *=0) | |
| Defaultconstructor. | |
| ~DataSetChainMember () | |
| Deconstructor. | |
| bool | event (QEvent *) |
| intercept to get events | |
Protected Member Functions | |
| virtual bool | dataArrived (NSCore::AcqisitionDataSet &)=0 |
| Data arrived! | |
Detailed Description
Consume datasets, do something with them and give them to the next consumer.Formerly there was producer and consumer and the chainmember to combine both. But consumers alone are stupid, even if things like the osci don't modify the data, they aren't always the last in the chain.
So the DataSetChainMember is the base class for elements consuming datasets, doing something with them and reaching them further down the chain.
Constructor & Destructor Documentation
| NSCore::DataSetChainMember::DataSetChainMember | ( | QObject * | = 0 |
) |
Defaultconstructor.
| NSCore::DataSetChainMember::~DataSetChainMember | ( | ) |
Deconstructor.
Member Function Documentation
| bool NSCore::DataSetChainMember::event | ( | QEvent * | ) |
intercept to get events
By this function we get notified of DataSetEvent signaling new data...
| virtual bool NSCore::DataSetChainMember::dataArrived | ( | NSCore::AcqisitionDataSet & | ) | [protected, pure virtual] |
Data arrived!
Subclass this function to handle the data. Return true when the data should be sent to the next in the chain. Otherwise it gets deleted.
Implemented in NSDiskIO::AbstractWriter, NSEvaluation::EvaluationPath, OsciWidgetV3_ChainMember, and ResultsToSpectrum.
The documentation for this class was generated from the following file:
