State

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

In LSL, most scripts sit idle until they receive some input, or detect some change in their environment. At any moment, the script is in some state, and will react to events or inputs according to some scheme defined by the programmer. However, a script can also contain two or more different states, and react differently to events or inputs depending on what state it is in.

The main state is the default state. When a script is compiled, reset or loaded, this is the state it enters by default. After the default state definition can follow additional state definitions which the script may use to change how and which events are handled.

The correct title of this article is state. The initial letter is shown capitalized due to technical restrictions.

default { events }

default { events }

• event

events

–

one or more events

The default state definition.

state target { events }

• label	target	–	state name
• event	events	–	one or more events

target state definition.

|- |

state target;

• label

target

–

name of a state to run

When a state target; is encountered at runtime, if the current state and the target state are different:

1. Trigger state_exit in the current state if it exists and clear the event queue.
2. Change state to target, any listens are unregistered.
3. Trigger state_entry in the target state if it exists.

If target state is the same as the current state, no state change occurs nor do any of the side effects.

Caveats

• On state change:
  • All listens are released.
  • The event queue is cleared.
  • Repeating sensors are released.
  • The timer event clock is not cleared.
• The default state must be defined before all others.
• States cannot have user functions or variables inside their immediate scope, only event definitions may be inside a states scope.

Examples

<lsl>default {

   touch_start(integer a)
   {
       state hello;
   }

}

state hello {

   state_entry()
   {
       llOwnerSay("Hello");
       state default;
   }
   state_exit()
   {
       llOwnerSay("Goodbye");
   }

}</lsl>

See Also

Keywords

•	jump
•	return

Events

•	state_entry
•	state_exit