Touch 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

touch_end

Description

! Event: touch_end( integer num_detected ){ ; }

4	Event ID
	Delay

Triggered when agent stops clicking on task

• integer

num_detected

Caveats

• When changing from a state that lacks a touch event into a state that has a touch event, the first touch will be dropped; this effects all three touch events (touch_start, touch, touch_end). See: SVC-3017
• If a prim face has Shared Media enabled and the avatar's viewer supports this feature, LSL scripts will not detect touches on that face. Touches from older clients will be detected.

Important Issues

~ All Issues ~ Search JIRA for related Bugs

SVC-3017

A

Server drops first touch event when a script returns to a state with a touch_start handler

Examples

You can use numbers 0 through num_detected - 1 with the various llDetected... functions to get detected agent keys etc. For most purposes, it is adequate to bother only with the first detected toucher e.g. llDetectedKey(0). It is rare (but not impossible) for num_detected to be other than 1. <lsl>

default {

   touch_start(integer num_detected)
   {
       llResetTime();
   }
   touch_end(integer num_detected)
   {
       llInstantMessage( llDetectedKey(0), "You held the mouse button down for " + (string) llGetTime() + " seconds");
   }

}</lsl><lsl>// If using a touch to change states be careful about the touch_ event order...

// On clicking a prim with touch events we trigger touch_start (as), touch (during) and touch_end (as released).

// The chain of events is established in the script as touch_start is triggered that remains intact until either

// touch_end is triggered or a new touch_start (discounting resets, deletions, taking to inventory etc.).

default {

   touch_start(integer nd)
   {
       llSay(0, "You just started touching me so I'm going to the other state...");
       state other;
   }

// A very rapid click would (and does if your VERY quick) beat the state change so the script would/does not behave as expected. } state other {

   touch_end(integer nd)
   {

// The average click will have you catapult through this state with nothing but a chatted message to remember it by.

       llSay(0, "The touch that brought you here just ended so I'm going back to default...");
       state default;
   }

}</lsl>

See Also

Events

•	touch_start
•	touch

Functions

•

llPassTouches

Deep Notes

Issues

All Issues

~ Search JIRA for related Issues

SVC-3017

A

Server drops first touch event when a script returns to a state with a touch_start handler

Signature
event void touch_end( integer num_detected );