Error 1034

Question

i am trying to bring over some classes i made in as2 to as3.
i've migrated everything appropriately but keep getting this error:
TypeError: Error #1034: Type Coercion failed: cannot convert
ball$ to flash.display.MovieClip. at
test_animateClass_fla::MainTimeline/frame1()
test_animateClass.fla has a movieclip called 'ball' in its
library that has linkage set to:
export for actionscript
export in first frame
class: ball
base class: flash.display.MovieClip
and the .fla loads an external class into it, Animate, which
then tries to use addChild() to add a copy of 'ball' to the stage
when it's created. a movieClip variable is passed into Animate()
from the .fla, which in this case, is the movieClip 'ball'.
why does it have this error converting 'ball' to
flash.display.MovieClip?? ball IS a MovieClip already..

Answer 1

quote:
Originally posted by:
shottogan
it is able to create a MovieClip from the passed through
variable with which it then visualizes itself through..
This is exactly why I don't see the value of this approach.
Why would you need to create a MovieClip from a passed variable? I
can see it only if, say, you load an external swf --> get class
definition from its library --> pass a CLASS into this function
--> instantiate this class.
If your Animate class is instantiated in the same swf where
the ball resides - your approach is a huge overkill because you can
instantiate ball directly inside Animate class. Based on the name
of the Animate class I assume you intend to animate a passed
variable. In this case - why not to instantiate and add to display
list ball and such in the scope where you instantiate Animate and
then just animate it? Or just pass an instance and place it in to
Animate's display list? But, again, since you attempt to place the
instance into the parent scope - why bother with all these
difficulties and not to place ball directly in the parent.
If you do not need to animate the instance - this approach is
a double overkill IMHO. AS3 handles positioning and other
DisplayObject properties beautifully. Its like putting microwave
into an oven to bake a cake inside microwave.
In any case I feel that something doesn't match up in this
approach. Of course, there is no information about context in which
you use it so all my thinking can be wrong.
By the way, I see a lot of complaints about Adobe removing
duplicateMovieClip method but so far the more I work with AS3 the
less I see a necessity for this functionality - things can be
easily instantiated AS3 native ways.