Thank you for the reply Stefan! To give you a bit more background, one of our projects seems to benefit a lot of osgEarth so I am looking into integrating OpenSceneGraph to our application (in fact, I already got a simple osgViewer-based integration working). What would be very nice is to be able to use things like OSG manipulators within an EQ application (especially for the osgEarth use case, since traditional 6-DOF manipulation really doesn't work well).
My main concern with keeping a local copy of the scene graph in the config's main thread is the "threat" of random OpenGL calls happening without the presence of an OpenGL context. Now, my understanding is that OSG doesn't really do that without an explicit request for a frame, but it still feels a bit "dirty" from a software engineering perspective to duplicate a piece of information that exists on the same machine and in the same process if there is a way to cleanly get access to it without hamstringing EQ's performance. -- View this message in context: http://software.1713.n2.nabble.com/Communicating-information-FROM-the-rendering-code-to-the-application-logic-tp7585385p7585388.html Sent from the Equalizer - Parallel Rendering mailing list archive at Nabble.com. _______________________________________________ eq-dev mailing list [email protected] http://www.equalizergraphics.com/cgi-bin/mailman/listinfo/eq-dev http://www.equalizergraphics.com
