Hi James, On 13 June 2012 20:21, James Adkison <jadki...@ara.com> wrote: > Per your request, I am following up on this as a reminder for you to look > into this and/or get the results of what you found.
Thanks for the reminder. Third time lucky :-) I spent a bit of time yesterday reproducing the problem, and this morning I sussed out the cause. Between 2.8.x and 3.x I revamped the way that event timing we done so that we didn't end up with negative time delta on events, such as getting events in after the frame has started, and with this the creation of the frame() event moved to the Viewer::advance() method. Unfortunately with this change the event state passed such as button mask assigned to the frame event came from the previous frames event state, rather the event state after looking at all the events for the current frame, this meant the button mask and mouse values ended up being one frame behind for the viewer's frame event. The solution was to move the frame() event call into Viewer::eventTraversal() and do it after the event state has been accumulated from the events collected from the windows. Could you try the svn/trunk version of the OSG to see if this works for you. Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
