The base structure that manages independent coroutines. For each handler, multiple threads (or in this case coroutine) can be created where each of them is in turn attached to a Script. This concept maximizes re-usability avoiding to have a large amount of duplicated code scattered among multiple scripts.

Handlers are attached to a multitude of resources such as Object and Asset, but are also contained in sub-resources (MiscType) like Action or Channel.

Static Variables

Name	Description
`lvmthread_count`	Current amount of LvmThread maintained by the active Handler.
Declaration unsigned char lvmthread_count
`localbounds`	Identifier of the underlying resource type associated to the current Handler.
Declaration unsigned int type Note The type can be either an AssetType or an ObjectType; special cases applied when the Handler is not directly associated with a resource perse which is identified by MiscType.

Functions

Name	Description
`AddThread`	Create a new LvmThread for the Handler to maintain.
Declaration LvmThread AddThread( const char name ) Parameters `name`: A unique name to identify the LvmThread within the Handler. Return Value A new LvmThread reference.
`GetThread`	Retrieve a specific thread by index.
Declaration LvmThread GetThread( const char name ) Parameters `name`: The Asset name or uid associated to the LvmThread. Return Value A valid LvmThread reference if the `name` matches the Asset connected to the active thread; else return `nil`.
`GetThreadAt`	Retrieve a specific thread by index.
Declaration LvmThread GetThreadAt( unsigned char index ) Parameters* `index`: The index of the LvmThread to retrieve. Return Value A valid LvmThread reference if the `index` is valid; else return `nil`.
`GetThreadIndex`	Retrieve the index of a specific LvmThread.
Declaration int GetThreadIndex( const LvmThread lvmthread ) Parameters* `lvmthread`: LvmThread reference to retrieve the index for. Return Value The index of the `lvmthread` received in parameter; else `nil` if the thread does not belong to the current Handler.
`SetThreadIndex`	Change the index of a specific thread.
Declaration bool SetThreadIndex( LvmThread lvmthread, const unsigned char index ) Parameters* `lvmthread`: LvmThread reference to switch to a new position. `index`: The position where the `lvmthread` should be placed. Return Value `true` if the operation was successfully executed; else return `false` if the `lvmthread` does not belong to the Handler or if the `index` is out of bounds.
`RemoveThread`	Remove a specific LvmThread from the Handler stack.
Declaration bool RemoveThread( LvmThread lvmthread ) Parameters* `lvmthread`: The LvmThread reference to remove. Return Value `true` if removed; `false` if the `lvmthread` is not associated to the current Handler.
`RemoveThreadAt`	Remove a specific LvmThread using its index.
Declaration bool RemoveThreadAt( const int index ) Parameters `index`: The index of the LvmThread to remove. Return Value `true` the thread pointed by `index` is removed; `false` if the index is invalid.
`SwapThreads`	Swap two LvmThread by index.
Declaration bool SwapThreads( unsigned char index0, unsigned char index1 ) Parameters `index0`: Index of the first LvmThread to swap. `index1`: The new position of the thread. Return Value `true` if swapped successfully; `false` either `index0` or `index1` is invalid.
`CanDispatchEvent`	Test if the Handler is responding to a specific EventType.
Declaration bool CanDispatchEvent( const EventType type ) Parameters `type`: The event type to test. Return Value `true` if the Handler can dispatch the event; else return `false`.
`DispatchEvent`	Manually dispatch either a C/C++ or Lua event.
Declaration void DispatchEvent( const EventType type ) Parameters `type`: The EventType to dispatch.
`DispatchEventC`	Manually dispatch a C/C++ event.
Declaration void DispatchEventC( const EventType type ) Parameters `type`: The type of event to manually dispatch.
`DispatchEventL`	Manually dispatch a Lua event.
Declaration void DispatchEventL( const EventType type ) Parameters `type`: The type of event to manually dispatch.

EventType

Type of events that a Script or a C/C++ plugin can respond to. To learn which resources respond to which callback check the Event section of its associated help page.

kOnStart: Application specific callback executed when the app. starts.
kOnStop: Application and playback specific resources (such as Channel, Sequence etc...) this callback executed once when the Stop function is called.
kOnLoad: Called when the Application is about to load a Scene.
kOnUnload: Called when the Application is about to unload a Scene.
kOnCreate: Specific to ParticleEmitter this callback is executed when new particles are created and for Object when it is constructed.
kOnDestroy: Called when a ParticleEmitter destroys particles, and for Object when it is about to be deleted by the scene garbage collector.
kOnDraw: Applied to resources that are drawing. This callback is called when a resource like Scene or Material, are ready to draw.
kOnDisplay: Also applied to resources that are drawing something; this function is called right after the draw.
kOnUpdate: Apply to all type of resources that need an update. This callback is triggered right after their update.
kOnBegin: Apply to Camera (before drawing to a FrameBuffer) and Scene (right before switching to the next RenderLayer)
kOnEnd: Apply to Camera (right after the FrameBuffer draw is executed) and Scene (right after finishing processing a RenderLayer).
kOnPlay: Specific to all resources that require a playback like SoundSource, Video, and ParticleSystem to name a few. This trigger is executed when the Play function successfully executed.
kOnPause: Specific to all resources that require a playback such as SoundSource, Video, and ParticleSystem etc... This trigger is executed when the Pause function successfully executed.
kOnResume: Specific to all resources that require a playback: SoundSource, Video, and ParticleSystem and the like. This trigger is executed when the resource state was paused and the Play function was called again.
kOnActuator: Channel specific triggered when the scrubber hit an actuator is encountered (see Channel for more information).
kOnEnter: Associated with ActionController (occur each time the controller enter a new state) and Region (a new Object enters the region).
kOnState: Happen each time an ActionController state is updated.
kOnLeave: Available for ActionController (the state is about to change) and Region (an Object leave the region).
kOnOverlay: Specific to Region; callback is triggered as long as at least one Object overlap the region.
kOnOverlap: Happens when two PhysicObject axis-aligned bounding box overlap.
kOnCollide: Occur as long as two PhysicObject are colliding.
kOnContact: triggered when contact between two PhysicObject happens.
kOnHit: Ray specific callback triggered upon a successful ray hit.
kOnProximity: Apply to Sensor, and is executed when a resource that has passed the filtering phase is inside the sensor radius.
kOnAdd: Happens when a new Object is added to a Scene.
kOnRemove: Happens when an Object is removed from a Scene.
kOnTrigger: Called each time a Sequence trigger is encountered.
kOnTouchesBegan: Manage by Application this callback is triggered when a touche or a mouse click happens.
kOnTouchesMoved: Application specific, triggered each time the active pointing device (mouse or touche) is moving on screen.
kOnTouchesEnded: Happens when then pointing device is released (Application specific).
kOnAccelerometer: Handled by the Application this callback is called on accelerometer update.
kOnGyroscope: Handled by the Application this callback is called on gyroscope update.
kOnGamepad: Application specific, this callback is triggered when a gamepad is connected or disconnected.
kOnGamepadAxis: Happens when a gamepad axis is pressed (Application).
kOnGamepadButtons: Happens when a gamepad button is pressed (Application).
kOnKeyboard: Application callback triggered when a keyboard key is pressed or released.
kOnIgnoreNotResponding: Prevent the built-in scripting mechanism to invalidate the LvmThread if it is not responding for more than 2sec. To deactivate this protection simply add at the top of your Script or Utility the following line: -- IGNORE_NOT_RESPONDING.