I've been using Eclipse, flashout, asdt, and MTASC to build some of my larger flash projects and one of the most annoying issues I have is the errors in the MM components, for example the TextInputBox references a _parent object that is out of scope in one of its methods but due to the macromedia compiler being very "loose" you get away with it when using the flash IDE. When use MTASC to compile you get compilation errors.
The MTASC -mx parameter makes MTASC use the precompiled components but still needs the MM component classes on the classpath, usually with
-cp C:\Program Files\Macromedia\Flash MX 2004\en\First Run\Classes
This works fine from the command line and I stop getting the annoying syntax errors, but when running inside eclipse with flashout and asdt I still get the errors when saving a file (I have my MTASC properies under "preferences|actionscript2|MTASC" to "Execute mtasc compiler on save".
I checked my flashout settings in project.flashout and it has the -mx flag enabled so what gives? Dummy, what I needed to do is add "-mx" to the MTASC settings under "preferences|actionscript2|MTASC" see screen capture I now remove the -mx flag from the flashout settings, see screen capture and now both save time compilation and publish time compilation don't complain about MM's messing component code :)
Comments