Hi James
I was playing with this the other night as well. The Lingo dictionary and
help files indicate this but never gives a thorough example as to how to
actually implement the procedure. My end result is similar to what you have
except that I set the timeOut period to 0 and just gave it a dummy
(non-existant handler) as you did. I wanted the timeOut object to remain
across multiple movies, so I did something like the following
property p_EventRedirector
on new me
p_EventRedirector = timeOut("Destructor").new(0, #void, me)
p_EventRedirector.persistent = TRUE
end
on remove me
p_EventRedirector.forget()
end remove
>From this point on, the object will recieve all prepareMovie, startMovie,
stopMovie, prepareFrame, enterFrame and exitFrame calls as if the object is
actually a movie script. It worked great.
For test purposes, I put in a dummy handler called on void me with output to
the mesage window for the purpose of detecting whether the timeOut object
was getting repeatedly called. The handler never resulted in any output so
it appears that a timeOut period of 0 will do exactly the same thing as
using the maxInteger, without the need to set the variable.
Obviously one wouldn't want to set the timeOut object to persistent unless
you wish it to exist across multiple movies as the timeOut list is auto
cleared when a movie ends ie. the stopMovie.
Thought I'd share this slight variation on the theme in case it interests
anyone else.
Sincerely
Mark
--------------------------------------------
Mark R. Jonkman
Mark R. Jonkman Consulting
ADDRESS: 20 Windermere Crt., Guelph, ON, CANADA N1E 3L4
PHONE: 519-837-8509
EMAIL: [EMAIL PROTECTED]
--------------------------------------------
[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!]
