Hi Mike. Thanks for taking time to reply...
if you follow the guidelines Flash will throw an error ->
var num:Number = 3;
var str:String = "Hello";
num = str;
Throws this error:
Type mismatch in assignment statement: found String where Number is required.
num = str;
Am I missing something?
Yes. Understood, thats my point.
The whole point of error checking is to catch when
the user didn't follow the guideline rules...
var Num:Number = 3;
Str = "Hello";
Num = Str;
...should never compile.
21) Changes to .as window is not seen until you save all vs.
coding directly in the fla which see it without needing to
constantly save. No idication that changes aren't included.
I don't know what you mean. Are you referring to working with external .as files? And when you say "changes" do you mean the testing the FLA in the authoring environment doesn't reflect any changes made to the .as file until you've saved that .as file? If that's the case, welcome to IDEs. I can't imagine a workable alternative. It's not like clicking File > Save All before you test is hard... But correct me if I'm missing something...
I've spent years in C++ Builder which has a real IDE with
tabbed windows. I can have 30 windows open and no matter
what code window I'm in it will compile that change.
File->Save everytime IS a major annoyance in large projects.
This allows for testing without committing to that change as
well as assurance that the developer is seeing all changes.
In Builder I can also run the app from any window I'm current
coding in.
I realize Flash isn't Builder, just I'm letting you know what
other developers expect from their IDE since MM is going
in that direction.
What I meant in my previous post about 'several version to MX2004'
are well known bugs that remain after several versions.
---
Even with all the problems I have with MX2004 if that undo
issue wasn't there I probably suffer through. That's the
real workflow killer I can't get around.
Again, thanks for your time.
Chris