This content has been marked as final. Show 7 replies
flash doesn't like it when you load into a parent AND a child movieclip.
so what is so bad about creating a partent clip, loading a file, then creating a child clip in it and loading another file? I find it to be a terrible limitation. Is there any way around this?
i don't see anything bad about it but flash sure doesn't handle the situation very well: if you load into the child first and then the parent, the child undergoes an unload. and that's not too helpful but there's nothing bizarre about that.
however, if you load into the parent first the child movieclip is totally removed and new movieclip with instance name mc1 and default properties is created as a child. and that's pretty bizarre.
anyway, i can't think of any reason to load into a child and a parent. to say the least, it would be problematic to control the properties of the child if you did anything to the parent.
so, just create movieclips that are children of some parent timeline and load into the children.
Hey kglad, does this also apply to attaching (via attachMovie() ) movieclips into one another? The op seems to be using the MovieClipLoader’s loadClip() to nest SWFs.
Ironically, why is it in the helpdocs that it mentions about SWFs under the attachMovie()? I thought attachMovie() only attaches symbols from the local or remote library.
no, there's no problem attaching a movieclip to a parent and then a child or to child and then a parent.
that's a typo in the help docs.
Nice, I understand now. Thanks kglad.
Damn deceiving helpdocs.