Timeout!

So I was having trouble getting llSetTimerEvent to work in this scrap of boolean tomfoolery and I hit on llSleep:

Slide()
{
if(!isOpen)
{
llSetPos(llGetPos() + delta);
llSleep(TimeInterval);
{
llSetPos(llGetPos() - delta);
}
}
}

Yes? No?

Why not? What was the question again?

Perhaps I'm overly cautious but I like to get a second opinion since I'm never quite sure what I'm doing with a script. In this case, llSetTimerEvent seems to have been created for just this purpose so I wanted to be sure I'm not doing something the system might regret someway down the line.

The timer is event based. As that the timer event handler will be called each time the set time has elapsed. In between other events can be handled by the script.
Apposed to that llSleep() holds the script for the specified time and the script will not do anything until the set time is over.
Only you will know what you want from the script and only you can decide what will suit your purpose best.

Thanks for the layman's explanation, Dora. In this case it's just about holding a door open so I can shift my pixel ass through. I guess it's ok then.

one thing to note... sleep has historically been a little less reliable for timing. it never under sleeps, but can frequently oversleep (especially at small intervals). so it's something to be aware of when using it.

Thanks for that, Void. In this case I won't worry even if it lags for a few seconds so long as the door closes eventually and provided I am not being chased indoors by a pack of wolves, of course - the last thing I need is to be locked indoors with a hungry horde.

I guess it's certainly something to watch for if the question of timing is sensitive.

Living with the script for a few days, the only thing that concerns me is I think the touch_end event will need to sleep also: I'm in the habit of touching to close so with this new version I keep setting off an it's-closed-no-it's-open-again-no-it's-ok-it's-closed-or-is-it-? kind of situation.

Sounds like me in the mornings!