The best way to handle the components would be to have the swc-files in the classpath, but as far as I know neither MTASC nor ASDT can "look inside" the swcs. Second best is to extract the as-files out of the swcs and have them in the classpath. Unfortunately ASDT doesn't allow me to se absolute classpaths in the project settings (I would say this is a bug). It claims that a directory doesn't exist even if it's obviously there. But with a relative classpath inside the eclipse-project environment ASDT finds the component types.
Gregor [EMAIL PROTECTED] wrote: >I just switched to ASDT 0.0.8 build 5 and when I've set it to compile a file >with MTASC when I hit save on the file. > >If my file contains > >import mx.controls.*; > >and in a class I declare > >private var foo:Label > >MTASC displays an error : > >type error, class not found :Label > >I have the -mx switch enabled for MTASC and I have the "Core" mm classes on >the mtasc setting in the dialog under "prefernces | ActionScript2 | Compiler | >Core path" > > >anyone figured this out ? I can compile fine when I use flashout, but doing a >"Save" with mtasc as the syntax checker gives me these errors. > >Grant, > > > > > > > > >------------------------------------------------------------------------ > >_______________________________________________ >osflash mailing list >[email protected] >http://osflash.org/mailman/listinfo/osflash_osflash.org > > _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
