mx::IErrorState Class Reference
[Component Interfaces]

Interface to objects supporting a special error state. More...

#include <IErrorState.h>

Inheritance diagram for mx::IErrorState:

mx::IInterface mx::IMxPEGParser mx::IMxPEGTileReceiver mx::IStreamSource mx::ISupportsShuttingDown mx::IUndecodedMxPEGFrameReceiver mx::MxPEGParser mx::BufferedMxPEGDecoderBackEnd mx::DiagnosticsMxPEGTileReceiver mx::IMxPEGRawFrameDumper mx::ISimpleMxPEGRenderer mx::IAsyncStreamSource mx::IStreamSourceFile mx::IStreamReceiver mx::IMxPEGScanDecoder mx::IMxPEGScanToJPEGConverter mx::MxPEGScanDecoderIPPCore mx::MxPEGScanDecoderSoftwareOnlyCore List of all members.

Public Member Functions

virtual bool errorState ()=0
 Tells whether or not the respective object is in error state.
virtual void setErrorState ()=0
 Switches the object into error state - needed for forwarding error conditions, see above.

Detailed Description

Interface to objects supporting a special error state.

Within a complex plugged-together decoding configuration (for example), it is possible that error conditions arise inside individual component objects. Those components can then switch to a dedicated error state which in most cases wil mean that they become inert. Their being in error state can be queries using the errorState() method.

For sequentially plugged-together object configurations such as decoder setups there is the convention that error states always get propagated through the sequence, so for the client context it will be sufficient to query the final element object to determine whether or not an error has been detected. It can then query the individual element objects to find out in detail what has gone wrong.

Author:
[khe] Kai Hergenroether


The documentation for this class was generated from the following file:
Generated on Fri Jun 29 17:21:05 2007 for MxPEG SDK by  doxygen 1.4.6