AS3's substitution of attachMovie for the movieclip constructor is,
while logical on the surface, somewhat baffling to me in practise. In
AS2, extending MovieClip required you to declare variables to gain
references to clips already instanced in the library movieclip. For
instance, extending a movieclip containing a textfield with instance
name "nameField" would require var nameField:TextField to gain control
of that field in the class. What this gives you on script level is an
overview of relevant movieclip members, as well as code completion. In
AS3, declaring variables to refer to hand placed movieclip members
throws an error:
1151: A conflict exists with definition x in namespace internal.
When using classes, go to your publish settings, actionscript, and turn
off "automatically declare stage instances" and it should behave as it
did before -- you'll need to declare stage instances yourself. I agree
that's odd, I use it off, but I guess they decided to add it on by
default is so beginners wouldn't have trouble dealing with elements when
coding 'on the timeline'.
Zeh
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
