RenderMan API
23.0
|
#include <RixInterfaces.h>
Classes | |
class | XcptHandler |
Public Member Functions | |
virtual void | Register (XcptHandler *)=0 |
virtual void | Unregister (XcptHandler *)=0 |
Unregister a msg handler. More... | |
virtual void | SetBuiltinHandler (RtUString name)=0 |
Public Member Functions inherited from RixInterface | |
virtual int | GetVersion () const |
Protected Member Functions | |
RixXcpt () | |
Protected Member Functions inherited from RixInterface | |
RixInterface (int version) | |
Interfaces should not be constructed by users. More... | |
virtual | ~RixInterface () |
Interfaces should not be deleted by users. More... | |
Additional Inherited Members | |
Public Types inherited from RixInterface | |
enum | Type { k_Float, k_Integer, k_StringV, k_Color, k_Normal, k_Vector, k_Point, k_HPoint, k_MPoint, k_Matrix } |
Protected Attributes inherited from RixInterface | |
int | m_version |
Version number of this interface. More... | |
The primary means to comprehend exceptional conditions within Rix is to handle messages generated by the library components. Clients should subclass RixXcptandler and register the object with the RixContext. Now they must carefully monitor the msg stream for severe conditions that might effect the use of the interfaces. In addition, lower-grade diagnostics should be reported through application-specific logging facilities.
Definition at line 188 of file RixInterfaces.h.
|
inlineprotected |
Definition at line 216 of file RixInterfaces.h.
|
pure virtual |
Register your msg handler to receive exceptions and diagnostics produced through the use of the Rix interfaces. Multiple handlers can be registered.
|
pure virtual |
Set one of the builtin error handlers
name | Values are: ignore, print, printonce, abort, or conditionalabort |
|
pure virtual |
Unregister a msg handler.