Thanks a lot Zeh, It worked nicely. I really appreciate you helping me out!
Initially, I wasn't targeting the individual "offending" child MCs with
stopTween(). BTW, I checked out your work, which is excellent. I even have
"Flash Hacks" in my library...
----- Original Message -----
From: "Zeh Fernando" <[EMAIL PROTECTED]>
To: "Flashcoders mailing list" <[email protected]>
Sent: Thursday, May 18, 2006 7:58 PM
Subject: Re: [Flashcoders] Problem with delayed Zigo Tweens
>I am having problems with a MC (instanceA) that has quite a few Zigo
>Tweens (ver. 1.2) on it's children MCs, with delay parameters spanning
>over approx. 90 seconds. InstanceA is one of 19 MC instances that sit on
>consecutive frames in the parent MC. This parent swf is loaded into an
>interface swf. In the interface, when I target the parent swf to go to a
>different frame (thus a different instance) before all the delayed tweens
>are completed in InstanceA, then return to InstanceA, the delayed tweens
>still seem to be in memory. How do I get rid of the delayed tweens when
>the mc instance is removed? I realize that ver. 1.2 has a cleanUp()
>function to remove uncalled delayed tweens when instances are removed,
>but it doesn't seem to be working properly.
Thanks in advance for any insight into this problem...
You can try doing a stopTween() on the 'offending' movieclips before
moving to the other frame, or immediatelly before a new frame is shown.
This removes all tweens for a given reference. It could be strange
depending on the number of movieclips you'll have to stop (you'll need
several lines of stopTween()s), but it's the cleanest way.
- Zeh
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
