Re: [SE|PY-macdev] Re: sepy-macdev digest, Vol 1 #105 - 9 msgs

[Jay M. <jay...@di...>]

Thank you, Loren.

Yeah, I totally misunderstood that. I was hoping that for those times that I
am not wanting to toggle between flash and Sepy that I could just check my
code there. The more I have looked the more I have realized that this is the
MO right now. I am writing Class files as well as basic AS2 files. Basic AS2
files are the main method that we build right no, and as you know the Flash
environment is not the most suitable for this. I was hoping that I could
build all my AS2 in Sepy and check it before I ran a compile on it. So, if
this is a possible feature in the future that would be highly requested from
MPOV. Anyway thank you for your insight and input.

I am loving this program. It makes writing external AS files much simpler
as well as more organized.

 
j



On 7/8/05 11:20 PM, "Loren Greenfield" <se...@in...> wrote:

> The first of your files is a class, the second is not, if you were to
> put "var myTest:test = new test();" within a class method, mtasc should
> valiadate it.
> 
> eg.
> 
> class MyOtherTestClass(){
> function MyOtherTestClass(){
> var myTest:test = new test();
> }
> 
> }
> 
> 
> 
> If you are using "var myTest:test = new test();" as an entry point
> (something to kick start the program), there is not reason to validate
> this in SEPY, just do it in Flash. If you are trying to compile with
> mtasc and not use Flash at all , I believe you have to enable entry
> point usage with mtasc, there is a good GUI that makes it easy. I've
> not really bothered with this though since most people using AS 2.0
> also have the Flash authoring enviroment.
> 
> To re-cap:
> 
> 1. mtasc is telling you that the keyword var is unexpected because it
> doesn't exist within a class.
> 2. Use mtasc to valiadate your classes
> 3. Use flash to validate non-class code
> 
> 
> Hope this answers your query.
> 
> 
> Loren Greenfield
> 
> 
> 
> 
> On 9/07/2005, at 3:36 PM, sep...@li...
> wrote:
> 
>> sorry, what i mean is that this file can be passed to mtasc without
>> problems:
>> -----
>> 
>> class Test(){
>>     function Test(){
>>        // my code.....
>>     }
>> }
>> 
>> -----
>> 
>> 
>> this file, instead, cannot be passed to mtasc:
>> -----
>> 
>> var myTest:test = new test();
>> 
>> -----
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
> July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
> core and dual graphics technology at this free one hour event hosted by HP,
> AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar
> _______________________________________________
> sepy-macdev mailing list
> sep...@li...
> https://lists.sourceforge.net/lists/listinfo/sepy-macdev

                   
Jay Myers
Design Specialist 
Direct: 816.512.9547

DigitalEvergreen 
423 West 8th Street
Kansas City, MO  64105
www.digitalevergreen.com