Data Structures | |
class | nrEngine::ScriptEvent |
Base event class for scripting engine events. More... | |
class | nrEngine::ScriptRegisterFunctionEvent |
Send this event by registering of a new function in the script engine. More... | |
class | nrEngine::ScriptRemoveFunctionEvent |
Send this event by removing of a function from the script engine. More... | |
class | nrEngine::KernelEvent |
On of the system base events classes (used by kernel to send information). More... | |
class | nrEngine::KernelStartTaskEvent |
Send this event if kernel start execution of a task. More... | |
class | nrEngine::KernelStopTaskEvent |
This event is sent if a task stopped/removed from pipeline. More... | |
class | nrEngine::KernelSuspendTaskEvent |
Task is get into sleep state now. More... | |
class | nrEngine::KernelResumeTaskEvent |
Event was waked up and is runnign now. More... |
The event interface is usefull for appropriate work of the engine. All events are handled in the background fully transparent to the user, so you do not have to care about them.
Some of the events could only be created by the system, so normal application is not allowed to send messages of this type. This is done by declaring the event constructor as protected/private, so only friend classes can create such events. You as normal user either don't need them or uncontrolled sending of them could cause system damage. However you are able to recieve the messages sended by the engine, if you need them this is another question ;-)