Sorry, I didn't intend to offend, hence why I put a ? at then end of my 
sentence. :)  Keep up the great work, looking forward very much to the Flash 9 
IDE! (which is when by the way? :) )

Jason Merrill
Bank of America 
Learning & Organization Effectiveness - Technology Solutions 
 
 
 
 
 

>>-----Original Message-----
>>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
>>Behalf Of sam / pixelconsumption
>>Sent: Tuesday, October 17, 2006 3:03 PM
>>To: Open Source Flash Mailing List
>>Subject: Re: [osflash] MTASC error
>>
>>Sloppy no, the Flash release was changing a lot when they were putting
>>in the v2 components that all items are not typed as they should be.
>>It's just a result of a having to make components while a compiler was
>>still being developed. The other issue is how mtasc deals with classes
>>and their imports. The patch will get you going.
>>
>>-Sam
>>
>>Merrill, Jason wrote:
>>>
>>> OK - I didn't know that, thanks. Apparently Macromedia wrote some
>>> sloppy code?
>>>
>>> Jason Merrill
>>> Bank of America
>>> Learning & Organization Effectiveness - Technology Solutions
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* [EMAIL PROTECTED]
>>> [mailto:[EMAIL PROTECTED] *On Behalf Of *John Grden
>>> *Sent:* Tuesday, October 17, 2006 2:14 PM
>>> *To:* Open Source Flash Mailing List
>>> *Subject:* Re: [osflash] MTASC error
>>>
>>> This from the list:
>>>
>>> You need all macromedia classes patched, because they aren`t mtasc
>>> compatible.
>>> look at http://osflash.org/mx_v2_components_patch for the latest patch.
>>> Then read & try to understand how mtasc works!, it´s pretty easy.
>>>
>>> Let me know if that helps,
>>>
>>> On 10/17/06, *Merrill, Jason* <[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]> > wrote:
>>>
>>> >> did you uncheck that in your new project or the global Properties?
>>> >>I think that's a little confusing to some people in FLASC
>>>
>>> Ok, I see. Regardless, I get Macromedia core class errors either way.
>>> I unchecked it in my individual project settings and now I get the
>>> same kind of "type" error, but for a different Macromedia core class:
>>>
>>> ../mx/core/ScrollView. as: 174...type error, Object should be a String
>>>
>>> Thanks for your help,
>>>
>>> Jason Merrill
>>> Bank of America
>>> Learning & Organization Effectiveness - Technology Solutions
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> *From:* [EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>
>>> [mailto:[EMAIL PROTECTED]
>>> <mailto:[EMAIL PROTECTED]>] *On Behalf Of *John Grden
>>> *Sent:* Tuesday, October 17, 2006 1:47 PM
>>> *To:* Open Source Flash Mailing List
>>> *Subject:* Re: [osflash] MTASC error
>>>
>>> did you uncheck that in your new project or the global Properties?
>>>
>>> I think that's a little confusing to some people in FLASC - the
>>> Properties>Default Tags are just meant to be used when you create a
>>> new project as your "Default" settings. But then after the project is
>>> created, it has it's own set of tags. So, be sure to edit the tags in
>>> your project (hold SHIFT+LMouse to edit a project)
>>>
>>>
>>> _______________________________________________
>>> osflash mailing list
>>> [email protected] <mailto:[email protected]>
>>> http://osflash.org/mailman/listinfo/osflash_osflash.org
>>>
>>>
>>>
>>>
>>> --
>>> [ JPG ]
>>>
>>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> 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

Reply via email to