Difference between revisions of "LlDetectedTouchUV"

From Second Life Wiki
Jump to navigation Jump to search
m (consistancy)
m (Edited the specification to note the variability of the vector components' intervals depending on face texture repeat values.)
Line 3: Line 3:
|func_id=337|func_sleep=0.0|func_energy=10.0
|func_id=337|func_sleep=0.0|func_energy=10.0
|func=llDetectedTouchUV
|func=llDetectedTouchUV
|return_type=vector|return_text=that is the texture coordinates for where the prim was touched. The {{LSLP|x}} & {{LSLP|y}} vector positions contain the {{LSLP|u}} & {{LSLP|v}} texture coordinates respectively (<code>{{NoWrap|{{LSL_VR|{{LSLPT|u}}|{{LSLPT|v}}|0.0}}}}</code>).
|return_type=vector|return_text=that is the texture coordinates for where the prim was touched. The {{LSLP|x}} & {{LSLP|y}} vector positions contain the {{LSLP|u}} & {{LSLP|v}} texture coordinates respectively (<code>{{NoWrap|{{LSL_VR|{{LSLPT|u}}|{{LSLPT|v}}|0.0}}}}</code>). Like [[llDetectedTouchST]], the interval of each component will be {{Interval|gte=0.0|center=component|lte=1.0}} unless the texture repeats are set to a non-default value. Increasing or decreasing the texture repeats of the face will change this interval accordingly.


{{LSL Const|TOUCH_INVALID_TEXCOORD|vector|{{LSL_VR|-1.0|-1.0|0.0}}}} is returned when the touch UV coordinates cannot be determined. See [[#Caveats|Caveats]] for further details.
{{LSL Const|TOUCH_INVALID_TEXCOORD|vector|{{LSL_VR|-1.0|-1.0|0.0}}}} is returned when the touch UV coordinates cannot be determined. See [[#Caveats|Caveats]] for further details.

Revision as of 11:29, 8 September 2012

Summary

Function: vector llDetectedTouchUV( integer index );
0.0 Forced Delay
10.0 Energy

Returns a vector that is the texture coordinates for where the prim was touched. The x & y vector positions contain the u & v texture coordinates respectively (<u, v, 0.0>). Like llDetectedTouchST, the interval of each component will be [0.0, 1.0] unless the texture repeats are set to a non-default value. Increasing or decreasing the texture repeats of the face will change this interval accordingly.

TOUCH_INVALID_TEXCOORD is returned when the touch UV coordinates cannot be determined. See Caveats for further details.

• integer index Index of detection information

index does not support negative indexes. For the touch category of events only. The prim that was touched may not be the prim receiving the event, use llDetectedLinkNumber to check for this; likewise you can use llDetectedTouchFace to determine which face was touched.

Caveats

  • If index is out of bounds the script continues to execute without an error message.
  • TOUCH_INVALID_TEXCOORD is returned when...
    • The avatar's viewer does not support face touch detection.
    • The touch has moved off the surface of the prim.
    • The touch happened too close to the edge of the face to determine a location.
    • The event triggered is not a touch event.

Examples

<lsl> default {

   touch_start(integer UV_detected)
   {
       integer i = 0;
       for(; i<UV_detected; ++i)
           llWhisper(0, "UV clicked: " + (string)llDetectedTouchUV(i));
   }

} </lsl> <lsl> default {

   touch_start(integer total_number)
   {
       vector UV = llDetectedTouchUV(0);
       float U = UV.x;
       float V = UV.y;
       // Now you can report U and V separately, or you can compare them separately with IF statements.
       // You of course do not need to store the vector components to separate variables,
       // you can access them from the vector that used as an intermediate, like this:
       // llSay(0, (string) UV.x);
   }

}

</lsl>

See Also

Deep Notes

History

Footnotes

  1. ^ The ranges in this article are written in Interval Notation.

Signature

function vector llDetectedTouchUV( integer index );