Moving end

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/pl 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

moving_end

Description

! Event: moving_end( ){ ; }

26	Event ID
	Delay

Triggered when task stops moving

Caveats

• The moving_start and moving_end events require special handling when scripting attachments.
  • After adding or editing a script you must:
    • Take off the attachment and then wear the attachment again.

• This event is also triggered when an object is rezzed (unless, presumably, you happen to rez it in precisely the same spot it was before.)

Important Issues

~ All Issues ~ Search JIRA for related Bugs

SVC-1004

A

Behavior of moving_start() and moving_end() is inconsistent.

Examples

See Also

Events

•

moving_start

Functions

•	llTarget
•	llRotTarget

Deep Notes

Issues

All Issues

~ Search JIRA for related Issues

SVC-1004

A

Behavior of moving_start() and moving_end() is inconsistent.

Signature
event void moving_end( );