TuttleOFX
1
|
The OFX suite that allows a plug-in to pass messages back to a user. More...
#include <ofxMessage.h>
Data Fields | |
OfxStatus(* | message )(void *handle, const char *messageType, const char *messageId, const char *format,...) |
Post a transient message on the host, using printf style varargs. Same as the V1 message suite call. | |
OfxStatus(* | setPersistentMessage )(void *handle, const char *messageType, const char *messageId, const char *format,...) |
Post a persistent message on an effect, using printf style varargs, and set error states. New for V2 message suite. | |
OfxStatus(* | clearPersistentMessage )(void *handle) |
Clears any persistent message on an effect handle that was set by OfxMessageSuiteV2::setPersistentMessage. New for V2 message suite. |
The OFX suite that allows a plug-in to pass messages back to a user.
This extends OfxMessageSuiteV1, and should be considered a replacement to version 1.
Note that this suite has been extended in backwards compatible manner, so that a host can return this struct for both V1 and V2.
Definition at line 122 of file ofxMessage.h.
OfxStatus(* OfxMessageSuiteV2::clearPersistentMessage)(void *handle) |
Clears any persistent message on an effect handle that was set by OfxMessageSuiteV2::setPersistentMessage. New for V2 message suite.
Clearing a message will clear any associated error state.
Definition at line 183 of file ofxMessage.h.
OfxStatus(* OfxMessageSuiteV2::message)(void *handle, const char *messageType, const char *messageId, const char *format,...) |
Post a transient message on the host, using printf style varargs. Same as the V1 message suite call.
Definition at line 138 of file ofxMessage.h.
OfxStatus(* OfxMessageSuiteV2::setPersistentMessage)(void *handle, const char *messageType, const char *messageId, const char *format,...) |
Post a persistent message on an effect, using printf style varargs, and set error states. New for V2 message suite.
Persistent messages are associated with an effect handle until explicitly cleared by an effect. So if an error message is posted the error state, and associated message will persist and be displayed on the effect appropriately. (eg: draw a node in red on a node based compostor and display the message when clicked on).
If messageType is error or warning, associated error states should be flagged on host applications. Posting an error message implies that the host cannot proceeed, a warning allows the host to proceed, whilst a simple message should have no stop anything.
Definition at line 164 of file ofxMessage.h.