I have two MTASC issues:
First, MTASC cannot compile MM's source for v2 components, because that
source itself does not comply to pure, strict AS 2.0. The workaround is
to use the -mx flag, which causes MTASC to use the precompiled .aso
objects for v2 components.
That's all well and good, but I need to alter the functioning of a
specific method in a specific class (I need the Tween class's
constructor to quit firing a start() command); and I can't extend and
override the method without MTASC trying to compile the base class and
barfing.
If anyone knows an MTASC-safe way of compiling v2 components, I'd like
to try it out. http://osflash.org/mx_v2_components_patch seems
interesting, for example. But...
Second, I wish to compile to a different location when I use MTASC. The
last time I tried MTASC, I found that the .aso files it produced caused
Flash to hang when I gave up and went back to MMC. If I could save MTASC
.aso files to a different location, leaving the old MMC ones untouched,
that would be pretty handy.
I could be wrong about this one, now that I think of it; what is the
relationship between MTASC and the compiled .aso files MMC generates? In
my understanding, MMC stores precompiled objects and re-uses those when
generating an SWF, assuming the actionscrip hasn't changed; MTASC does
the same, right?
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
