Wacky. Thanks for looking further into this. It's helping to
understand the issues, for sure... not to say that I'm fully aware of
what to do with this knowledge so far, but thanks. :)
Paul
John VanHorn wrote:
here, i set the frame rate to 1, and tried to move the mouse 1 px
persecond.
i added traces for everything on both enterframe and mousemove events.
you
can start to see the asychronicity between setting the text and redrawing
the stage:
onEnterFrame
mc._x: 3.45
_xmouse: 149
text: 4
onMouseMove
mc._x: 3.45
_xmouse: 150
text: 4
onEnterFrame
mc._x: 4.45
_xmouse: 150
text: 4
onEnterFrame
mc._x: 4.45
_xmouse: 150
text: 4
onMouseMove
mc._x: 4.45
_xmouse: 149
text: 5
onEnterFrame
mc._x: 3.45
_xmouse: 149
text: 5
On 2/28/07, Alain Rousseau <[EMAIL PROTECTED]> wrote:
onEnterFrame didn't give any better results either, it was definitely a
case of how fast can Flash grab the exact _x postion when the button is
released and the listener removed (or onEnterFrame deleted). Can't quite
understand the logic of the sequence or timing, but it's definitely a
case of asynchronous function call.
John VanHorn wrote:
> this seems to be tied to using a mouse listener. onMouseMove is not
> synchronous with the frame rate, so it can fire more than once in
between
> frames....that being said, it still doesnt make sense that the _x
> seemingly
> increases if you drag left.
>
> if you use good ole onEnterFrame, everything works fine.
_______________________________________________
[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
