Changing the subject since this is a different topic.
Werner Modenbach writes:
> Can you please give a compareable short explanation on how frame() calls are
> generated and what happens inside then?
> The background of my question is the behaviour and the experience I got with
> Qt Adapterwidget. There we have a timer calling frame() every xx msec.
> On many systems this drives CPU activity to almost 100% - even if nothing
> happenes and nothing changed in the scene.
The best way of seeing it is in the source code. frame() is not a
complicated function at all, but launches the update, cull and render
traversals every time it is called. Obviously, if nothing in your scene
changes and you don't need to redraw, you could avoid calling it.
This is a snippet from frame (ViewerBase.cpp):
eventTraversal();
updateTraversal();
renderingTraversals();
--
Alberto
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
