I always forget to mention that. I do have an edited post around here somewhere on this subject. That only works online as it has to be a browser viewing the files on a server, for it to actually pass those variables to the new swf.
During creation and test phases, I usually have something in the first line of the first frame of the movie that I’m loading the variables into like so…
This ensures that whatever is loading this movie, if it has called out to it with a ?=klfdshgklj those variables will be loaded, by this simple set variable statement.
Later, at upload time, I slash these out with comment tags like so.
- //Comment tags delete anything that is to the right of them from swf production.*
- //in this case the variable that I have loaded using a ?=something statement*
- //in file name “blablabla.swf”*
now none of that will be in the swf. It doesn’t take any room in a produced peice, but, it does explain when you have the file open in Flash, what the code is for, and why it’s commented out.
Reusability is again the key. If I want to retool this FLA, I need to know that it’s getting some code from somewhere else.
Granted in this simple an example, you’re not likely to forget what’s going on… but imagine a site with 200 swfs and associated pics or html, or xml…
… as you go on you’ll need comment tags… use em now, cause they only help.