my impression of this is that if you have static variables or methods of the moveclip then you have a class that extends MovieClip?
if so, my suggestion is make sure the references to the class are set to null / out of scope - in my experience unloading a class that extends MovieClip does not always delete the reference to the associated subclass of MovieClip hth - and might be barking up the wrong tree rob ________________________________ From: [EMAIL PROTECTED] on behalf of Matthias Dittgen Sent: Thu 1/10/2008 2:20 AM To: Flash Coders List Subject: [Flashcoders] Re: AVM1Movie unload and static variables In fact this problem applies not only for AS2/AS3 interop. How can I unload MovieClips and thus unload static variables to have a fresh startover, when loading the same MovieClip later again? Matthias On Jan 9, 2008 3:32 PM, Matthias Dittgen <[EMAIL PROTECTED]> wrote: > Hello Flashcodes, > > I isolated a recent problem I had using AVM1Movies. I have build this > everywhere mentioned Proxy for "old" Flash content (Flash8 and > before), that enables my AS3 Application to communicate with the > loaded AS2 based MovieClip using LocalConnection. > > Now I load an "old" Movie for the first time into an own container > within my proxy AVM1Movie and I lockroot it, too. Later the Movie gets > unloaded and sometime later the Movie ist loaded again to a new > container. The second time, the Movie does NOT work as expected, > because static variables from its former incarnation are still set. > > Questions: > Why are these variables still there and not deleted by garbage > collection or the like? > How can I have it work? Is there more than lockroot, I can do? > > Any help or comment on this is welcome. > > Matthias > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Important - This email and any attachments may be confidential. If received in error, please contact us and delete all copies. Before opening or using attachments check them for viruses and defects. Regardless of any loss, damage or consequence, whether caused by the negligence of the sender or not, resulting directly or indirectly from the use of any attached files our liability is limited to resupplying any affected attachments. Any representations or opinions expressed are those of the individual sender, and not necessarily those of the Department of Education and Early Childhood Development.
_______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
