Hi John, The OSG is design to have three main phase - update, cull and draw. The update phase includes the update traversal of the scene, and the event traversal - this phase is deliberately single threaded as to avoid the need to multi-buffer the scene graph. The cull-draw traversals can safely run multi-threaded as they are read only.
The EventQueue itself support multi-threaded reading and writing, that is you can write to it from one thread, and read from it from another. The thread reading it will be the one doing the update and event traversals, the thread filling it might be this same thread or a background thread. The event traversal doesn't and shouldn't run in parallel to the cull-draw though. As to whether this at all related to what you are trying to achieve I can not say, I'm not familiar with qtosgwidget. Robert. On 1/16/07, Whitfield, John M. (SED/TMI) <[EMAIL PROTECTED]> wrote:
I was looking more into the operation of qtosgwidget, and it uses the eventqueue to keep up with mouse inputs. Is there a chance that this is preventing the mouse inputs from being process before the end of its drawing operations? If so does anyone know a way around this, or to make it check the que while its drawing? Thanks, -John _______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
_______________________________________________ osg-users mailing list osg-users@openscenegraph.net http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
