Of course, now that MovieClipSprite no longer subclasses EventDispatcher it will no longer accept an event listener or dispatch MouseEvent3D. Are we supposed to be using a different approach?
On Apr 3, 10:34 pm, wagster <[email protected]> wrote: > Well I think I've found the answer. In the docs here: > > http://away3d.com/livedocs/3.5.0_lib/away3d/sprites/MovieClipSprite.html > > it gives the inheritance as > > MovieClipSprite -> Object3D -> flash.events.EventDispatcher > > which would give it all the addListener functions you could shake a > stick at. But if you look at the source code, the actual inheritance > is now > > MovieClipSprite -> Sprite3D -> Element > > which is a different matter altogether. Quick update of the docs > would be handy when you get a moment. > > Cheers! > > On Apr 2, 9:01 pm, wagster <[email protected]> wrote: > > > This seems like a really basic AS3 question, and possibly it is, but I > > can't figure it out for the life of me. > > > I'm calling > > > sign3d.addOnMouseDown(onMouseDown); > > > where sign3d is a MovieClipSprite - but I'm getting a compiler error > > of > > > 1061: Call to a possibly undefined method addOnMouseDown through a > > reference with static type away3d.sprites:MovieClipSprite. > > > Firstly, this is a defined method of MovieClipSprite - it's in the > > reference and the source code (I'm compiling from a swc rather than > > the source code, but still, I can't believe it's just been taken > > out). So why can't the compiler see it? > > > Secondly, what is the advantage of calling addOnMouseDown over just > > adding a listener in the usual manner? > > > Thanks.
