LlSensorRemove

Template:Needs Translation/LSL/de Template:Needs Translation/LSL/es Template:Needs Translation/LSL/el Template:Needs Translation/LSL/he Template:Needs Translation/LSL/it Template:Needs Translation/LSL/ko Template:Needs Translation/LSL/nl Template:Needs Translation/LSL/hu Template:Needs Translation/LSL/no Template:Needs Translation/LSL/da Template:Needs Translation/LSL/sv Template:Needs Translation/LSL/tr Template:Needs Translation/LSL/pl Template:Needs Translation/LSL/pt Template:Needs Translation/LSL/ru Template:Needs Translation/LSL/th Template:Needs Translation/LSL/uk Template:Needs Translation/LSL/zh-Hans Template:Needs Translation/LSL/zh-Hant

/LSL

SensorRemove

llSensorRemove

Summary

Function: llSensorRemove( );

0.0	Forced Delay
10.0	Energy

Removes the sensor setup by llSensorRepeat.

There are no parameters or return value for this function, as only one llSensorRepeat can be specified per script.

Caveats

• If called within the sensor event then it also removes all of the sensor data that is accessed by the detection functions.

Examples

The following basic example shows an object that when touched starts scanning for avatars in 10m every 30 seconds, and stops as soon as at least one is found, and returns their name. <lsl>default {

   touch_start(integer x) {
       llSensorRepeat("", NULL_KEY, AGENT, 10.0, PI, 30.0);
   }

   sensor(integer x) {
       key id = llDetectedKey(0);
       string name = llGetDisplayName(id);

if (("" == name)

See Also

Events

•

sensor

Functions

•

llSensorRepeat

–

Scans for agents or objects every time period

Deep Notes

Signature
function void llSensorRemove();

Haiku
Call off the hounds. The quarry has escaped us. Back to the stables.