 | | | memory management - removeMovieClip / | memory management - removeMovieClip /
2004-02-21 - By Lindsey Simon
Back
delete
Reply-To:
In-Reply-To: <200402190939218.SM01784@(protected) >
X-OS: Linux chiefy 2.4.23
X-mailer: Mutt 1.5.5.1+cvs20040105i (2003-11-05)
I really would love to see some more dialogue on this subject.
One thing I 've found is that even with unloadMove and removeMovieClip,
there are still pointers recursively existing for the object following
those methods. Which makes me think they 're still in memory and
thereby sucking. So, before I removeMovieClip I recurse through the
object and remove movie clips, text fields, and then use delete on the
references. I use a few prototypes I wrote to do this and I think
they 're ugly, but I believe they are working.
Does anyone else want to share their wisdom on this - I 'd like to come
up with a nice function to completely obliterate a movie clip and all
of it 's functions, textfields, properties, etc.. recursively. i.e. for
it 's children.
I don 't want to burden the list with a huge bunch of code unless this
topic is of interest to others.
-l
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Supported by Fig Leaf Software
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
Be sure to check the archives and the wiki:
http://chattyfig.figleaf.com/
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
http://chattyfig.figleaf.com/cgi-bin/ezmlm-cgi?1:mss:104901
=-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --
To unsubscribe send a blank e-mail to:
Normal Mode: flashcoders-unsubscribe@(protected)
Digest Mode: flashcoders-digest-unsubscrive@(protected)
|
|
|