Open GoogleCodeExporter opened 9 years ago
You can get around this by commenting out the checks on hasMouseMoved() in
handleMouseOver and handleMouseOut in InteractiveSceneManager
Obviously this means more load on cpu as it is doing the check all the time,
but it
might help someone.
Neil
Original comment by neilbrow...@googlemail.com
on 14 Jul 2009 at 11:22
have an other issue with the version 2.0883 (windows xp):
when the event MOUSE_OUT is fired, there is in the same time an MOUSE_OVER
fired ...
Can't have a single event Mouse_out without having mouse_over in the same
time...
I don't understand why the mouse_out mouse_over events are handeled with
ENTER_FRAME
?
sebastien
Original comment by sebasti...@gmail.com
on 5 Aug 2009 at 11:46
thank you neil!!!
Original comment by alessfl...@gmail.com
on 8 Sep 2009 at 11:44
Original issue reported on code.google.com by
fabio.ca...@gmail.com
on 1 Jul 2009 at 5:37Attachments: