Difference between revisions of "TOUCH INVALID VECTOR"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
m |
|||
| Line 11: | Line 11: | ||
{{LSL DefineRow||[[llDetectedTouchBinormal]]}} | {{LSL DefineRow||[[llDetectedTouchBinormal]]}} | ||
|caveats=*For [[llDetectedTouchPos]], {{LSL VR|0.0|0.0|0.0}} may be a valid value so it is possible to get a false negative in this rare situation. | |caveats=*For [[llDetectedTouchPos]], {{LSL VR|0.0|0.0|0.0}} may be a valid value so it is possible to get a false negative in this rare situation. | ||
| | |deepnotes=Has the same value as {{LSL Const|ZERO_VECTOR|vecter|{{LSL_VR|0.0|0.0|0.0}}}}. | ||
|events | |events | ||
|cat1=Touch | |cat1=Touch | ||
Revision as of 01:16, 13 September 2008
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Description
Constant: vector TOUCH_INVALID_VECTOR = <0.0, 0.0, 0.0>;The vector constant TOUCH_INVALID_VECTOR has the value <0.0, 0.0, 0.0>
Returned by llDetectedTouchPos, llDetectedTouchNormal, and llDetectedTouchBinormal when the touch position is not valid.
Caveats
- For llDetectedTouchPos, <0.0, 0.0, 0.0> may be a valid value so it is possible to get a false negative in this rare situation.
Related Articles
Functions
| • | llDetectedTouchPos | |||
| • | llDetectedTouchNormal | |||
| • | llDetectedTouchBinormal |
Deep Notes
Has the same value as ZERO_VECTOR.
History
- Introduced in
SVN:1167 r96080 Branch:viewer_1-21-2 Tuesday, 09 September 2008 - Merged into Trunk
SVN:1169 r96492 Branch:{{{branch}}} Thursday, 11 September 2008
Search JIRA for related Issues
Signature |
|---|
vector TOUCH_INVALID_VECTOR = <0.0, 0.0, 0.0>; |