Difference between revisions of "No sensor"
Jump to navigation
Jump to search
All Issues ~ Search JIRA for related Bugs
m |
(fix variable name mismatch in code snippet) |
||
| Line 36: | Line 36: | ||
if(data == []) | if(data == []) | ||
return 0; | return 0; | ||
return llVecDist(llList2Vector(data, 0), llGetPos()) <= | return llVecDist(llList2Vector(data, 0), llGetPos()) <= distance; | ||
}</lsl> | }</lsl> | ||
|also_header | |also_header | ||
Revision as of 07:42, 15 September 2012
| LSL Portal | Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials |
Caveats
- sensor/no_sensor are not always the best solution:
- To determine if something is in/out of range is overkill. For this situation use: llGetObjectDetails as you will see in the Useful Snippets section.
- To determine if an avatar is in the region, try llGetAgentSize
Examples
<lsl>//List all avatars in range. default {
on_rez(integer i) {
llSensor("", "", AGENT, 100000, 10000);
}
sensor(integer num) {
integer i = 0;
do {
llOwnerSay(llDetectedName(i) + " is " + (string)llVecDist(llGetPos(), llDetectedPos(i)) + "m away.");
}while(++i < num);
}
no_sensor() {
llOwnerSay("No avatars in range.");
}
}</lsl>
Useful Snippets
<lsl>//An alternative solution for find out if a user is not in range //No sensor is used so the above caveat doesn't apply.
integer InRange(key uuid, float distance) {
list data = llGetObjectDetails(uuid, [OBJECT_POS]);
if(data == [])
return 0;
return llVecDist(llList2Vector(data, 0), llGetPos()) <= distance;
}</lsl>
See Also
Functions
| • | llSensor | |||
| • | llSensorRepeat |
Deep Notes
Issues
All Issues
~ Search JIRA for related Issues
|
|
SVC-2409 | A | llSensorRepeat not triggering no_sensor unless a sensor event handler is present |
Signature |
|---|
event void no_sensor( ); |