Thanks for the pointers Jakob, I have tracked down the source of the
error, should have looked a bit harder at what was going on in the
de-bugger. What happens is that when I call the
interval = timeOut("textTO").new(3000, #tPause, me)
director is calling my global <on timeOut> handler which I'm using as a
general timeout script for when the kiosk is inactive. Is this supposed
to happen? I can't see why anyone would want it to happen, or am I just
getting caught up in a destructive thought-loop. The new timeOut object
method is unrelated to the old <on timeOut> handler, isn't it?
Hmmm, so how would I be able to have the 2 sorts of timeOut in one
movie? Back to the drawing board... some kind of encapsulation I guess
freaked-out
Jon Rowe
> -----Original Message-----
> From: Jakob Hede Madsen [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, October 10, 2000 1:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: <lingo-l> timeOut object
>
>
> Just a hunch:
> Is your parent script actually a Movie script?
> Declaring a global 'new' handler could probably lead to errors.
>
> Jakob
>
> [To remove yourself from this list, or to change to digest mode, go to
> http://www.penworks.com/LUJ/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!]
>
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/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!]
