Maybe you can inform Adobe about it, since it seems like a bug in their
compiler, unless i'm missing something. Create a zip of the current
distribution to be able to demonstrate this problem. Maybe Mike Chambers
can forward it to the compiler crew.
r.
Ralf Bokelberg wrote:
> Hi iiley,
>
> i took a look at the example named Test and it fails indeed in MMC.
> I found out, that there is a problem with the initialization order of
> the classes. Currently the classes are initialized like this:
>
> EventDispatcher
> MCPanel
> Component
> Container
>
> The problem is, MCPanel extends Container, but Container isn't
> initialized yet. So the extension fails. You can verify this by checking
> myPanel instanceof Container, which fails too.
>
> Seems like MMC can't find the correct order. Maybe it has to do with
> your way to initialize static variables: static myStatic = new
> OtherClass();
> I never analyzed it thoroughly, but in the past i often encountered
> problems when i did the same. Solution is to do it explicitely in some
> static initializeClass method.
>
>
> Hope it helps,
> r.
>
>
>
> iiley wrote:
>
>
>>We talked some at ActionStep alpha1 thread, i don't want to mess the
>>thread since this is not about actionstep.:)
>>For a pain of making ASWing compatible with MMC, i notice that there are
>>less people feel same like me, haven't seen a man got pain about this on
>>this list, is it only my problem?:) However, maybe you can help us about
>>this. And also i can share some experiences about this maybe can help you.
>>
>> From MTASC to MMC:
>>
>>To make a FAME project compatible with MMC(FlashIDE?),I know if compile
>>as files with flash2004 compiler :
>>First thing you should make sure all of your as files are UTF8 encoding,
>>and with a UTF8-BOM( with"EFBBBF" 3 byte at the beginning of the file),
>>you can selected "Force creation of UTF-8 BOM" checkbox in ASDT Editor
>>Options or "Create BOM in as-Files with UTF-8 encoding" checkbox in FDT
>>preferences. Notice it is "EFBBBF", not "FFFE", if you use UltraEdit to
>>view the Hex, it viewed "FFFE", it is not the truth. This step is boring
>>if your project is big, although, it can be fixed easily. You can write
>>a programe to do the conversion.
>>
>>Second, of course make sure you are not using MTASC especial features,
>>like miss semicolon at the end of the line, or if you are using old
>>version of MTASC you can define properties in interfaces, add a otiose
>>comma in array define like [a, b, c, ]. Fortunately most uncompatible
>>features are gone from newest version of MTASC, this step is easy.
>>
>>After they two step, you can compile your project with MMC now, There is
>>no error or warnning when compiling. but i can't assure the compiled swf
>>will works as same as compiled with MTASC. ASWing project is a sample.
>>
>> From MMC to MTASC:
>>
>>There are many experiences can be found at mtasc list, here i post two
>>tips what i think is most should be took noticed.
>>Don't assign values to member fields like:
>>class A{
>> var v:Number = 0;
>>}
>>You should do it in the constructor functions.
>>
>>Take care to assign values to class fields like:
>>class A{
>> static var v:B = new B();
>>}
>>if v is a string or number there is no problem, but if it is a complex
>>type(your definded class), there may have problems.see the details at
>>"Bug of creating instance for static var" threads in MTASC List.
>>
>>Hope this is helpful for some guys, and also, hope you can share your
>>Experiences or problems here. Maybe your experiences can help us to
>>solve the problem of ASWing's.
>>--
>>iiley
>>AsWing http://www.aswing.org
>>Blog http://spaces.msn.com/members/iiley/
>>
>>
>>------------------------------------------------------------------------
>>
>>_______________________________________________
>>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
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
