You will find the working demonstration of the code I've discussed at the beginning of this article.
SubClass instance = new SubClass(parm1, parm2.) YOU SHOULD NOT : Pass Constructor Arguments Into a MovieClip SubClass using the traditional constructor-argument type of instantiation:.Some_mc.attachMovie(linkageName, instanceName, depth, PARAMS) YOU SHOULD : Pass a PARAMS Object into the MovieClip's SubClass for instantiation using another MovieClip's parameters argument.Rules For Constructing a SubClass of MovieClip: The object, so cleverly named, 'PARAMS', must get passed into the subclass via another MovieClip's attachMovie method in order for the SubClass MovieClip to initialize correctly.Initial values must also be set to the PARAMS object properties, these are the values that correspond with the properties of the SubClass that you wish to populate upon this, pseudo instantiation.The PARAMS object property names correspond with your SubClass property names.Var PARAMS:Object = new Object() someMc.attachMovie(subClassMcLinkageName, subClassInstanceName, someMcDepth, PARAMS) The MovieClip and it's SubClasses Construct via PARAMS Object that gets passed into another MovieClip's attachMovie method.Here are my lessons learned listed for you in the hopes that they save you some stress as you develop your ActionScript Programming skills. The biggest challenge with Extending MovieClip, is that it does not use it's constructor to instantiate, as other classes are wont to do.
#Flash actionscript 3.0 invalid xml name full#
I hope that you will gain encouragement and momentum from this knowledge, and I wish you a journey full of epiphanies, as you develop your ActionScript Programming skills going forward. I hereby take responsibility to share with you all of the lessons that I've learned about this subject so that you will know what to watch out for as you grow your own skill set. With this power and respect, comes the weight of responsibility. It also offers the developer more flexibility, and opens up a world of potential for your next ActionScript Flash Application. It gives your clip clout, demanding respect from all of the lesser MovieClips on the stage. There is a lot of power in Extending MovieClip. OO ActionScript has finally arrived, and none too late! Don't get me wrong, I am a hardcore ActionScript programmer, I've hung in there by a thread, and now that ActionScript 3.0 has finally arrived with Flash CS3, I can breath a sigh of relif. The reasoning behind giving the MovieClip a 'Monster' status is because the MovieClip object does not behave like any other OO Class and due to it being at the core of Flash, and ActionScript Programming, I would imagine that it has caused it's share of headaches to more people than just me. Given the combination, and the often over trusted Object Oriented promises of ActionScript 2.0, anyone with a solid programming background would be a bit surprised, at the very least, by the behavior of this 'MovieClip Monster'. Veteran 4GL programmers, OO Framework gurus, and other geeks far and wide would gasp and pale if they knew what implications the title of this article brought with it.
0 kommentar(er)
