Difference between revisions of "Category:LSL Events"
m |
Omei Qunhua (talk | contribs) m (typo, clarification) |
||
| (5 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{LSL Header|ml=*}} | {{LSL Header|ml=*}} | ||
Within | Within [[state]]s LSL works on events, such as the scripted object starting to move ([[moving_start]]), colliding with things ([[collision_start]]) or a recurring timer ([[timer]]). | ||
Events do not interrupt each other, but instead are queued {{HoverText|FIFO|First In, First Out}}. On state change the event queue is cleared and any open listens are [[llListenRemove|removed]] automatically. Reoccurring events ([[sensor | Events do not interrupt each other, but instead are queued {{HoverText|FIFO|First In, First Out}}, though the [[state_entry]] event can jump the queue. If more that 64 events are waiting, new events are discarded until free slots become available. If the script is paused, such as when an object is taken to inventory, pending events are preserved and handled the next time the object is rezzed. | ||
On state change the event queue is cleared and any open listens are [[llListenRemove|removed]] automatically. Reoccurring sensor events ([[sensor]]) are set not to reoccur in the new state and must be manually re-enabled (via [[llSensor]] or [[llSensorRepeat]]), but timer events (from [[llSetTimerEvent]]) ''do'' reoccur. Please refer to the [[State]] article for further details. | |||
For legacy LSL - the events are registered as bit flags in an unsigned-64 bit integer, meaning there can only ever be 64 events. | |||
{{KBtrivia|<b><code>event</code></b> is a reserved word in LSL, but it is not used. If you try to use it as a function or variable name, it will cause a syntax error.}} | |||
{{LSLC|Keywords}} | {{LSLC|Keywords}} | ||
{{LSLC|}} | {{LSLC|}} | ||
Latest revision as of 07:29, 13 May 2014
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Within states LSL works on events, such as the scripted object starting to move (moving_start), colliding with things (collision_start) or a recurring timer (timer).
Events do not interrupt each other, but instead are queued FIFO, though the state_entry event can jump the queue. If more that 64 events are waiting, new events are discarded until free slots become available. If the script is paused, such as when an object is taken to inventory, pending events are preserved and handled the next time the object is rezzed. On state change the event queue is cleared and any open listens are removed automatically. Reoccurring sensor events (sensor) are set not to reoccur in the new state and must be manually re-enabled (via llSensor or llSensorRepeat), but timer events (from llSetTimerEvent) do reoccur. Please refer to the State article for further details.
For legacy LSL - the events are registered as bit flags in an unsigned-64 bit integer, meaning there can only ever be 64 events.
 |
Trivia: event is a reserved word in LSL, but it is not used. If you try to use it as a function or variable name, it will cause a syntax error. |
Subcategories
This category has the following 10 subcategories, out of 10 total.
Pages in category "LSL Events"
The following 44 pages are in this category, out of 44 total.