This content has been marked as final. Show 3 replies
It is simple. I think that you may be over-thinking the problem.
If you want to use loadMovie() from one Flash .swf in Director to load
in another Flash .swf, then just use the relative path from the first
.swf to the second .swf. The first .swf must be linked and not fully
loaded into the Director movie.
When you go to import the first .swf, be sure to set the option at the
bottom left of the import window to "Link to External File". Then keep
that first .swf file next to the Director movie, or in a folder, if you
like. Be sure to not move the .swf file after you link it to the
So, if you have your Director movie, myMovie.dir and a linked Flash
movie, flash1.swf next to that in a folder, and another Flash movie,
flash2.swf, in the same folder, then the call to load in the second
movie would be:
When you move all of the files to a server, or to a CD, be sure to keep
all of files in the same relative location as they were during authoring.
Adobe Community Expert
Hi, thank you, Rob! It helped me tremendously to have that shown to me. Upon reading your response, I became a little concerned about being able to load in SWF files from, say, an installed location or a central location on a network. But first, I simply did what you said -- and it worked first time out -- then I started fiddling with an absolute pathname, e.g.:
... and it worked as well. I also tried...
...and it worked.
What was I doing wrong? In my case, since I am working with a program that I also want to have be able to load SWFs in from a web server, I was re-using:
loadMovie(targetFile, _level0, "GET");
... and specifying file URLs without success. The problem was that third param. With it present, external SWFs won't load from the local file system properly. Remove it, and bingo, you're in business!
Seems pretty obvious in hindsight...! :-P
Upon further consideration, I guess you could say it was "GET" ting in the way....! :-)