Difference between revisions of "Touch end"
Jump to navigation
Jump to search
Omei Qunhua (talk | contribs) (Remove reference to inaccurate misleading Jira issue. Clarify state change advice.) |
Lady Sumoku (talk | contribs) m (Replaced old <LSL> block with <source lang="lsl2">) |
||
| 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. | ||
< | <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"); | ||
} | } | ||
}</ | }</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. | ||
Revision as of 00:04, 22 January 2015
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Caveats
- 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.
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.
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");
}
}
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.
- On clicking a prim with touch events we trigger touch_start (on first contact), touch (during) and touch_end (as released).
See Also
Deep Notes
Signature |
|---|
event void touch_end( integer num_detected ); |