Hi! I'm currently working on a cube primative that loads a MovieClip
instance on each side of the cube (except top and bottom). The
MovieClip contains two buttons for navigation (previous and next) to
rotate the cube. It works quite well but I discovered a bug:
The button's position is always the same and if you click the next
button and don't move the mouse you have to click twice (or move the
mouse a bit) to dispatch the second "next event". Does anybody have an
idea if it's a bug in the away3d framework or rather a bug caused by
my decent event propagation skills? - Greets

Reply via email to