 | | Re: some information about timeout objects (was: Re: [dirGames-L]
Kill Child f | Re: some information about timeout objects (was: Re: [dirGames-L]
Kill Child f 2003-12-12 - By steve
Back
Great, thanks for the info! I'm thinking of a few applications of the second
timeOut method you mentioned already.
On an off-topic note... as an insider, do you think there will ever be the
posibility of Macromedia combining the Flash plugin and Shockwave plugin
into one? I realize the Shockwave plugin allows for certain system-level
functionality that is not available in Flash... but it's a pipe dream.
Steve
-- -- Original Message -- --
From: "Thomas Higgins" <thiggins@(protected)>
To: <dirgames-l@(protected)>
Sent: Friday, December 12, 2003 1:48 PM
Subject: some information about timeout objects (was: Re: [dirGames-L] Kill
Child from within parent)
> All,
> First off, this is my first time back on this list since late last year
when
> I left for some holiday time. I've been back at work for a number of
months
> but just never got around to rejoining this list. Due to some chatter
> elsewhere I've decided it was time to get back on this list and hopefully
> lend a hand now and again (not to mention gleaning all your tips and
> tricks!).
>
> The specific issue that we were discussing is timeout objects and a few
bits
> about their functionality that have been missing from our documentation
for
> quite some time and that have for the most part been lost from general
> knowledge. Hopefully the info I'm about to share will prove useful. I'm
> already working with our support team to get a tech note written about
this
> in addition to our docs team so that this is included in our docs for the
> next release of Director.
>
> Timeout Object Tidbits
> There are two general syntax options you can use when creating a timeout
> object. They are:
>
> tTO = timeout(someName).new(period,targetHandler,targetScriptObject)
> tTO = timeout(someName).new(period,targetHandler,timeoutData)
>
> What? What's timeoutData all about? Hang on, I'll get there... When you
use
> the first option above the timeout object will fire off the specified
> handler in the target script object (which must be an instanced script,
i.e.
> a behavior, a parent script, etc.). If you want custom properties
associated
> with your timeout object the assumption is that you'd make them properties
> within the target script object. When you use the second option, and
provide
> as the "target" anything other than a reference to an instanced script,
then
> that "target" data becomes data associated with the timeout object that
can
> be used in your timeout handler. Sweet. Here is an example:
>
> -- somewhere in my code I initialize the timeout object
> -- and pass it a data list
> tData = [#beta: 0]
> tTO = timeout("foo").new(50,#targetHandler,tData)
>
> -- then elsewhere in my movie, within a movie script, I
> -- write the following handler
> on targetHandler (aData)
>
> -- increment and display the beta property
> tData.beta = tData.beta + 1
> put(tData.beta)
>
> end targetHandler
>
> Do the above and watch your message window, beta keeps incrementing! This
> means you can initialize several timeout objects, all calling the same
movie
> script handler, each having its own data list associated with it. Nice.
But
> wait, there's more I'd like to share about timeout objects.
>
> If you specify an instanced script object as the target of your timeout
> object, not only will that script object recieve the timeout event, but it
> will recieve the following movie and frame events:
>
> - prepareMovie, startMovie, stopMovie
> - prepareFrame, exitFrame
>
> That means you must be careful when targeting a script object as you can
get
> two exitFrame calls per frame if your target is a behavior with an
exitFrame
> handler (the handler gets called once for the timeout object then again
for
> the general frame event). The idea behind this was that timeout objects
were
> meant to replace actorList objects, allowing you to use time-based event
> calling as opposed to frame-based event calling. Then folks wanted their
> timeouts to know about various other events when targeting an instanced
> script, from that came the choice of events above.
>
>
> Both of the items I mentioned above, passing a data list to a timeout
object
> as well as the movie and frame events that get triggered, are _not_
> mentioned in the documentation and I don't know that they ever have. Ugh.
As
> mentioned above I'm working with the folks in tech support to get a
technote
> written about this as well as our documentation team to get this in the
> manuals/help for the next release.
>
> Hopefully I'm chiming in on target as I'm flying mostly blind (thanks to
> Chuck Neal and Alex da Franca for providing a few source posts for
> reference). I'm busy on a few lists so I don't anticipate being the most
> active list poster but I do try to be an avid reader if nothing else. If a
> particular thread is in dire need of Macromedia attention and I'm not on
the
> ball, gimme a poke at thiggins@(protected)
>
> Peace y'all.
>
>
> Cheers,
> Tom Higgins
> Product Specialist - Director Team
> Macromedia
>
> DIRECTOR, de lekkerste!
>
> ...
>
> __ ____ ____ ____ ____ ____ ____ ____ ____ ____
> dirGames-L mailing list - dirGames-L@(protected)
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames-l
__ ____ ____ ____ ____ ____ ____ ____ ____ ____
dirGames-L mailing list - dirGames-L@(protected)
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames-l
Earn $52 per hosting referral at Lunarpages.
|
|
|