Problem with llSensorRemove

I don't understand this at all. I've been putting in some debug-type llSay commands to track the execution of my code, and this is what is happening:

1) llSensorRepeat is called with a 1 second scan time.
2) The first line of the Sensor event is an llSay for tracking purposes.
3) I call llSensorRemove in a listen event.
4) The line after that is another llSay, which executes.
5) I then get the llSay from the Sensor event.

But I canceled the sensor! Why does it execute one more time? Is there a delay in llSensorRemove?

Objects do not "hear" themselves. So your listen code is not executing.

No, it's listening to me.

But I found the answer. Sensor repeat calls are queued, and it can be that some stick in the queue after llSensorRemove is called. One has to add an extra variable to track if the sensor is supposed to be running or not.

Yeah any time you initiate something to call an event handler you have to assume it happens out of order. So the easiest way do deal with that would be:

FROM:

touch_start(int num)
{
llSensor()
stuffForAfterSensor();
}

sensor(){
llSay("one";
}

TO:

touch_start(int num)
{
llSensor()
}

sensor(){
llSay("one";
stuffForAfterSensor();
}

That will chain your functionality so it occurs in the expected sequence. I'm not sure if that is useful or not for you though.