On 8/21/06, [b) a d i <[EMAIL PROTECTED]> wrote:
the problem i have is after calling removeMovieClip or delete is that when i need to re-instantiate the object...it's either corrupt or not created properly...i was a little upset to find so many dangling pointers after i went thru so much trouble to clean up after myself...
I can't think of a circumstance where this could happen - could you give us an example? (Assuming AS2...) In short, for 'normal' Flash objects (i.e. those created with new SomeObject()) you're quite correct, there's no destructor; as with many similar languages, there's garbage collection system. When nothing is referencing an object, it gets stuck on the garbage collection list, and will be properly deleted and the memory freed up when the Flash Player gets around to it (you can't guarantee exactly when) For MovieClips created with attachMovie or createEmptyMovieClip, they're removed from the display list and destroyed using removeMovieClip(); any dangling references you have to the clip will become invalid. HTH, Ian _______________________________________________ [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
