Nowadays,I recommend you to avoid using Flashout and use instead ASDT SWFViewer and AS Logger. To automatize the compilation process I recommend you to use an ANT script, in order to separate the build process from the Eclipse IDE.
See this article as a possible guide: http://osflash.org/asdt/logging?s=logger Hope that helps. C. 2005/11/2, Justin Clarke <[EMAIL PROTECTED]>: > Hi there, > I've got a problem that's surely been answered, but after searcing high > and low I can't find the answer. I've been doing Flash dev using Eclipse > etc and loving it, but now I've got to the stage in a project where I > need a button component. I've added that to the library from within MM's > IDE, and when I compile the first time in Eclipse it's fine - I use the > -mx switch to avoid errors and everythings a-ok. But every compile after > that the swf causes the "A script is running slowly..." message, and > debug statements get outputted multiple times, as if there are multiple > versions running at the same time within the swf. I actually have to go > back into the MM IDE, recompile the original swf, and then I'm able to > compile again in Eclipse (once, of course, before it starts tanking again). > > After reading up on this I thought the answer was to keep the source swf > generated by MM IDE untouched, and use the -out option in MTASC to > generate a new file. This works fine, except that within Eclipse the > Flashout displays the source swf, not the -out putted swf. If anyone > can point out the correct way to add components I would be very > grateful, because I clearly haven't found the solution! > > cheers, > justin. > > > _______________________________________________ > osflash mailing list > [email protected] > http://osflash.org/mailman/listinfo/osflash_osflash.org > -- ::| Carlos Rovira ::| http://www.carlosrovira.com _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
