Difference between revisions of "Talk:Attach"
m |
|||
| Line 10: | Line 10: | ||
:I would have said that if the event took longer then 0.1 (I'm guessing) seconds to run then it would pause execution of the event and detach. -- [[User:Strife Onizuka|Strife Onizuka]] 06:38, 21 June 2008 (PDT) | :I would have said that if the event took longer then 0.1 (I'm guessing) seconds to run then it would pause execution of the event and detach. -- [[User:Strife Onizuka|Strife Onizuka]] 06:38, 21 June 2008 (PDT) | ||
I'm noticing that even with attach not doing much, it does not run at all when an avatar is logging out. Is this a new and permenant behaviour? | |||
Revision as of 17:57, 19 January 2010
In order for the attach() event to trigger while detaching, it must delay the detach long enough for it to process its contents.
There are a few things, such as processing time and certain functions, that will cause the detach to happen immediately while processing detach events. The next time the object is rezzed or attached, it will continue mid-event until it finishes, then begin the next event in the queue: on_rez(), then attach() (if it was attached).
What are the details of detach delay? I know that calling llSleep() while detaching will immediately stop the execution and detach the object. I've also noticed that calling llStartAnimation() and llStopAnimation() with an invalid animation will result in a script error, a script delay, and immediately stop further processing.
Is it as simple as "anything with a script delay causes immediate detachment"?
--Stickman Ingmann 20:24, 20 June 2008 (PDT)
- I would have said that if the event took longer then 0.1 (I'm guessing) seconds to run then it would pause execution of the event and detach. -- Strife Onizuka 06:38, 21 June 2008 (PDT)
I'm noticing that even with attach not doing much, it does not run at all when an avatar is logging out. Is this a new and permenant behaviour?