Difference between revisions of "Moving end"

From Second Life Wiki
Jump to navigation Jump to search
Line 5: Line 5:
|spec
|spec
|caveats=*The [[moving_start]] and [[moving_end]] events require special handling when scripting attachments.
|caveats=*The [[moving_start]] and [[moving_end]] events require special handling when scripting attachments.
**After adding or editing a script you must:
**After adding or editing a script you must take off the attachment and then wear the attachment again.
***Take off the attachment and then wear the attachment again.
*This event's behavior is undefined for non-physical movement ([[llSetPos]], movement via [[Building_Tools|build tool]], etc.)
*This event's behavior is undefined for non-physical movement ([[llSetPos]], movement via [[Building_Tools|build tool]], etc.)
*This event is triggered when an object finishes its [[LlSetKeyframedMotion|keyframed motion]], or when motion ceases via KFM_CMD_PAUSE or KFM_CMD_STOP, in the same region the motion begins.
*This event is triggered when an object finishes its [[LlSetKeyframedMotion|keyframed motion]], or when motion ceases via KFM_CMD_PAUSE or KFM_CMD_STOP.
**If the region crosses a sim border during movement, it appears to internally "reset" the moving state, and moving_end is not triggered.
*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.)
*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.)
|examples=<lsl>
|examples=<lsl>

Revision as of 15:59, 29 October 2012

Description

! Event: moving_end( ){ ; }

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's behavior is undefined for non-physical movement (llSetPos, movement via build tool, etc.)
  • This event is triggered when an object finishes its keyframed motion, or when motion ceases via KFM_CMD_PAUSE or KFM_CMD_STOP.
  • 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.)


Examples

<lsl> //Physical Prim Movement Script //By Nika Rugani //With spam work around

vector pos; float move_time = 5; //Move every 5 seconds float increment = 5;

float power = 0.5; //The TAU

integer trigger_multiple = FALSE; // This bad boy will prevent spam of moving start event integer trigger_slave = 1;

setPhysical(integer status_physics) {

   llSetLinkPrimitiveParamsFast(LINK_THIS, [PRIM_PHYSICS, status_physics]);

}

default {

   touch_start(integer num_detected)
   {
       if(llGetStatus(STATUS_PHYSICS) == FALSE)
       {
           pos = llGetPos(); //Set the objects default position
           setPhysical(TRUE);
           llSetTimerEvent(move_time);
       }
       else
       {
           setPhysical(FALSE);
           llSetPos(pos);
       }
   }
   moving_start()
   {
       if(trigger_slave == 0)
       {
           llOwnerSay("YEY!! I'm Moving!");
           if(trigger_multiple == FALSE)
           {
               trigger_slave = 1;
           }
       }
   }
   moving_end()
   {
       llSetTimerEvent(move_time);
   }
   timer()
   {
       llSetTimerEvent(0);
       if(llVecDist(pos, llGetPos()) > (increment-2))
       {
           llMoveToTarget(pos, power);
       }
       else
       {
           llMoveToTarget(pos+<0.0,0.0,increment>, power);
       }
       trigger_slave = 0;
   }

}</lsl>

See Also

Events

•  moving_start

Functions

•  llTarget
•  llRotTarget

Deep Notes

Issues

All Issues

~ Search JIRA for related Issues
   Behavior of moving_start() and moving_end() is inconsistent.

Signature

event void moving_end(  );