Touch end - Revision history

Wulfie Reanimator: Added new example (moved from Touch)

2026-04-30T07:13:26Z

Added new example (moved from Touch)

← Older revision		Revision as of 00:13, 30 April 2026
Line 6:		Line 6:
	\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.		\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.
	* Rigged mesh attachments do not support touch events, this is because you can steer your avatar/camera by click dragging your avatar body which is what the rigged mesh replaces. The only way to get a touch event on a rigged mesh attachment is via the right click context menu and clicking the "Touch" button.		* Rigged mesh attachments do not support touch events, this is because you can steer your avatar/camera by click dragging your avatar body which is what the rigged mesh replaces. The only way to get a touch event on a rigged mesh attachment is via the right click context menu and clicking the "Touch" button.
	\|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.		\|examples=You can use index 0 through (<code>num_detected</code>-1) with the various llDetected... functions to handle simultaneous touches at once.

			For most purposes, it's usually enough to handle just with the first toucher e.g. [[llDetectedKey]](0). It is rare (but not impossible) for <code>num_detected</code> to be greater than 1.
	<source lang="lsl2">		<source lang="lsl2">

	default		default
	{		{
Line 15:		Line 16:
	llResetTime();		llResetTime();
	}		}

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

			This next example demonstrates detecting when the owner of the object clicks-and-holds on the object for 1 second in order perhaps to access a management menu or similar, Normal brief clicks are distinguished.
			<source lang="lsl2">
			default
			{
			touch_start(integer num_detected)
			{
			llResetTime(); // Set llGetTime to 0
			}

			touch_end(integer num_detected)
			{
			// Check how much time elapsed since touch_start
			if (llGetTime() <= 1.0)
			{
			// The user did a normal quick click on the object
			// Execute actions for normal clicks...
			}
			else
			{
			// The owner has touched this object for longer than 1 second
			// Execute some special feature such as issuing a management dialog...
			}
			}
			}
			</source>
	\|notes=*If using a touch to change states be careful about the touch_ event order. '''The best advice is NOT to do state changes from within touch_start.''' Use touch_end and do the state change there. Changing state from within touch_start can cause the next occurrence of THAT touch_start code to be missed.		\|notes=*If using a touch to change states be careful about the touch_ event order. '''The best advice is NOT to do state changes from within touch_start.''' Use touch_end and do the state change there. Changing state from within touch_start can cause the next occurrence of THAT touch_start code to be missed.

Nexii Malthus: **

2025-08-26T12:17:26Z

← Older revision		Revision as of 05:17, 26 August 2025
Line 5:		Line 5:
	\|spec		\|spec
	\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.		\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.
			* Rigged mesh attachments do not support touch events, this is because you can steer your avatar/camera by click dragging your avatar body which is what the rigged mesh replaces. The only way to get a touch event on a rigged mesh attachment is via the right click context menu and clicking the "Touch" button.
	\|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.		\|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.
	<source lang="lsl2">		<source lang="lsl2">

Strife Onizuka at 05:07, 2 January 2016

2016-01-02T05:07:24Z

← Older revision		Revision as of 22:07, 1 January 2016
Line 39:		Line 39:
	\|cat2=Detected		\|cat2=Detected
	\|cat3=Grab		\|cat3=Grab
	\|cat4}}		\|cat4=Passable
			}}

Lady Sumoku: Replaced old block with

2015-01-22T08:04:20Z

Replaced old <LSL> block with <source lang="lsl2">

← Older revision		Revision as of 01:04, 22 January 2015
Line 6:		Line 6:
	\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.		\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.
	\|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.		\|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~~>		<source lang="lsl2">

	default		default
Line 18:		Line 18:
	llInstantMessage( llDetectedKey(0), "You held the mouse button down for " + (string) llGetTime() + " seconds");		llInstantMessage( llDetectedKey(0), "You held the mouse button down for " + (string) llGetTime() + " seconds");
	}		}
	}</~~lsl~~>		}</source>

	\|notes=*If using a touch to change states be careful about the touch_ event order. '''The best advice is NOT to do state changes from within touch_start.''' Use touch_end and do the state change there. Changing state from within touch_start can cause the next occurrence of THAT touch_start code to be missed.		\|notes=*If using a touch to change states be careful about the touch_ event order. '''The best advice is NOT to do state changes from within touch_start.''' Use touch_end and do the state change there. Changing state from within touch_start can cause the next occurrence of THAT touch_start code to be missed.

Omei Qunhua: Remove reference to inaccurate misleading Jira issue. Clarify state change advice.

2012-12-27T11:24:25Z

Remove reference to inaccurate misleading Jira issue. Clarify state change advice.

@@ Line 1: / Line 1: @@
-{{Template:Issues/SVC-3017}}{{LSL_Event|event_id=4|event_delay|event=touch_end
+{{LSL_Event|event_id=4|event_delay|event=touch_end
 |p1_type=integer|p1_name=num_detected|p1_desc
 |event_desc=Triggered when agent stops clicking on task
@@ Line 17: / Line 17: @@
+     {
          llInstantMessage( llDetectedKey(0), "You held the mouse button down for " + (string) llGetTime() + " seconds");
+     }
 }</lsl>
 |helpers
 |also_header

Omei Qunhua: More sensible use of Time functions in 1st example. Clarify num_detected in practice.

2012-12-25T00:23:13Z

More sensible use of Time functions in 1st example. Clarify num_detected in practice.

← Older revision		Revision as of 17:23, 24 December 2012
Line 5:		Line 5:
	\|spec		\|spec
	\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.		\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.
	\|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:		\|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>~~float t;~~		<lsl>

	default		default
Line 12:		Line 12:
	touch_start(integer num_detected)		touch_start(integer num_detected)
	{		{
	~~t = llGetTime~~();		llResetTime();
	}		}
	touch_end(integer num_detected)		touch_end(integer num_detected)
	{		{
	~~llOwnerSay~~((string)(llGetTime(~~) - t~~) + " seconds ~~between touch_start and touch_end~~");		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...		}</lsl><lsl>// If using a touch to change states be careful about the touch_ event order...

Cerise Sorbet at 21:59, 3 March 2010

2010-03-03T21:59:49Z

← Older revision		Revision as of 14:59, 3 March 2010
Line 4:		Line 4:
	\|constants		\|constants
	\|spec		\|spec
	\|caveats=If a prim [[face]] has [[Navigating Shared Media\|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.		\|caveats=* If a prim [[face]] has [[Navigating Shared Media\|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.
	\|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:		\|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:
	<lsl>float t;		<lsl>float t;

Cerise Sorbet at 21:58, 3 March 2010

2010-03-03T21:58:45Z

← Older revision		Revision as of 14:58, 3 March 2010
Line 4:		Line 4:
	\|constants		\|constants
	\|spec		\|spec
	\|caveats		\|caveats=If a prim [[face]] has [[Navigating Shared Media\|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.
	\|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:		\|examples=You can use numbers 0 through num_detected - 1 to get detected agent keys:
	<lsl>float t;		<lsl>float t;

Fred Gandt: and here too

2010-01-31T09:40:51Z

and here too

← Older revision		Revision as of 02:40, 31 January 2010
Line 32:		Line 32:
	llSay(0, "You just started touching me so I'm going to the other state...");		llSay(0, "You just started touching me so I'm going to the other state...");
	state other;		state other;
	}// A very rapid click would ~~theoretically~~ beat the state change so the script would not behave as expected.		}
			// 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		state other

Fred Gandt: and again

2010-01-31T08:53:12Z

and again

← Older revision		Revision as of 01:53, 31 January 2010
Line 18:		Line 18:
	llOwnerSay((string)(llGetTime() - t) + " seconds between touch_start and touch_end");		llOwnerSay((string)(llGetTime() - t) + " seconds between touch_start and touch_end");
	}		}
	}</lsl><lsl>// ~~A minor concern~~ to ~~take note~~ of...		}</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		default
	{		{
Line 26:		Line 32:
	llSay(0, "You just started touching me so I'm going to the other state...");		llSay(0, "You just started touching me so I'm going to the other state...");
	state other;		state other;
	}		}// A very rapid click would theoretically beat the state change so the script would not behave as expected.
	}		}
	state other		state other
Line 32:		Line 38:
	touch_end(integer nd)		touch_end(integer nd)
	{		{
	llSay(0, "The touch that brought you here just ended so I'm ~~off~~...");		// 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;		state default;
	}		}