C API (Component Interface)
The module should instantiate a new component and return it in
event->object. This object will be passed back to the module in future in the context of each further event fired on this component instantiation. Finally, the same object will be passed to a paired call to EVENT_MODULE_DESTROY when its work is done.
The module should also return
ComponentInfo for the new component object.
This event is fired multiple times shortly after module loading to instantiate as many copies of a component as the executed system requires.
Symbol hComponent IN
- This is the symbol (handle) of the new component, and should be stored for later use in calls to the framework.
ComponentCreate* create IN
- Specific information on creation. Currently, there is nothing of use here to the native component - this data is used by language bindings only.
ComponentData* data IN
- Component-specific data; this pointer may be kept and dereferenced at any time later to obtain the framework-maintained data for this component. You should NOT keep the pointers that are fields of
data, since these may become invalid on later calls - only keep the pointer
ComponentInfo* info IN
- The module should return a pointer to a structure filled with component information. The pointer must be valid for the lifetime of the component.
- Store any of the passed information that is required in future.
- Prepare a component information structure (if not pre-prepared).
- Return a pointer to this structure.
- Create a new component and store it in
This is the implementation used in the 1199 bindings.
C++ API (1199)
= (EventModuleCreate * )