On Monday, Aug 9, 2004, at 02:44 US/Eastern, S�bastien Portebois wrote:
This is only a blind guess, but are youreally sure that your new (moved) idel handler really gets called?
Indeed a possible eplanation of what happens is that you have an other 'on idle' handler, in a script after the very long one, but before the new placed you've put the 'on idle sleep' handler.
So when the firs idle handler found by Director is the one containins the sleep, you get an error, but when you moved it, you don't get the error, simply because this moved handler don't get called anymore, because another 'on idle' handler is found before by the Director player.
Does this make sense?
Hi Seb,
<grin> I wish it was that easy.
Only one "idle" handler for sure. I thought of that and did a quick "Find" just to make sure.
I'm thinking (guessing) it's a weird "timing" thing that might have something to do w/the way Director loads Xtras.
When the "on idle" handler was all the way at the end of the movie script, an error (mentioning another, unrelated Xtra) kept getting thrown right after the projector launch. Moved the "on idle" handler to the top, error went away. Move it back, error comes back.
In authoring, I got a different sort of error...when the "on idle" handler was at the bottom, Director didn't even recognize "sleep" as a valid function - even though "sleep" and various other UIhelper functions I tested worked just fine in the message window. When I moved the "on idle" handler to the top, the problem went away.
Weird, huh?
Gilles
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
