Hi Tamer, Thanks for spotting this regression. The bug came about due to me tightening up the event traversal so that it only handles events uptill the viewer.advance(), which prevents events having negative times w.r.t the frame event. Unfortunately this fix meant that no events were being processed when using --run-on-demand as this support doesn't event advance the frame till an event comes in.
I have changed the cutoff time for events for the case of --run-on-demand so it behaves the way it used to. Robert. On Tue, Jun 21, 2011 at 4:44 PM, Tamer Fahmy <tamer.fa...@gmail.com> wrote: > Hi all, > > tested OpenSceneGraph 3.0-rc2 on Ubuntu 10.10 with NVidia 270.41.19, > which builds and runs just fine. > > However, I noticed that (at least on my system) trying to run e.g. > 'osgviewer --run-on-demand cessna.osg' renders the first frame just > fine, but then apparently frame updates aren't triggered by any further > input events. > > Reverting the changes of src/osgViewer/Viewer.cpp and > src/osgViewer/CompositeViewer.cpp from r12523 to the previous r12294 > makes it work again. > > Anyone else able to reproduce that behavior, too? > > Thanks for all the great work on OpenSceneGraph and good luck with the > upcoming release, > tamer. > > > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
