5 replies to this topic

[Daedality]

Okay, so http://www.freewebs....opean/index.htm (Yeah, I know, I know. I just threw it on a freewebs 'cause it's fast and easy to FTP)

You may have to refresh if the window doesn't pop up, I have a javascript code that opens the SWF in a new window.

So, anyway, I'm using an SWF, a loader. It loads the other SWF using loadMovie, and it works great! Problem is, once it's all loaded, the buttons from the SWF that got loaded don't work.

And yes, they work on the original SWF. This is really starting to chap my ass, I can't figure it out.

[Pax]

Hows the movie setup that you are using loadmovie in? Is there a layer above what you load the new swf into that contains a button? Any element that has any sort of button action (release, rollover, roll out, etc) will override any button events of elements below it.

[Daedality]

It's set up

*actionscript
*shell movie
*dynamic text
*progress bar
*bg

And there are no buttons above shell movie, if that's what you mean.

[Pax]

Same version of flash? Sometimes loading a flash 6 file into flash 8, or the other way around will break stuff. Another thing that might be breaking it is in the swf you are loading, does it use _root at all?

[Daedality]

Uhh... Yeah, it does use _root. And they're both flash 8. How would I go about correcting it?

[Pax]

Well, you could use _lockroot = true;

But that is a hack. Its bad practice to use _root at all. I would suggest you use proper referencing. Use _parent to navigate back up the movie clip hierarchy until you get to _level0 (or root), which will then be _level1 when loaded into the other mc.

Use trace statements to find out where _parent points to, and figure out how many _parent's youll need. Just use _parent._parent etc. Attach as many as you need.

Of course, you'll probably just use lockroot, but *shrug* I'll still tell you what the better idea is Gl mate.