Hi John, I do plan on adding sort order control into the GraphicsContext list of GraphicsOperations such that when the GraphicsContext::runOperations() is ran both the Camera's associated with the context and the operations will be sorted w.r.t to each other. I have plenty of other tasks pending so I don't know when I'll be able to get to this.
As others have suggested the Camera::setFinalDrawCallback() is probably sufficient if you want to do screen capture. The osgscreencaputre example in SVN, uses this. Robert. On Wed, Jun 18, 2008 at 8:36 PM, Argentieri, John-P63223 <[EMAIL PROTECTED]> wrote: > Robert/OSG, > > What is the plan for OSG to grant us the ability to insert custom graphics > operations in a controlled order? What I mean is, what if we want to process > our own application-level callbacks immediately after makeCurrent() and > immediately before swapBuffers() using osgViewer::CompositeViewer? > > There are too many things that we can't do using osgViewer::CompositeViewer > and Camera/Cull callbacks. > > osgViewer::CompositeViewer doesn't permit us to do image->readPixels in > order to do a screen capture. I've read all your advice on the topic in this > forum. It just doesn't work. > > We have to roll our own render loop to the point that I never even call > renderTraversals(). I made my own method that substitutes that method. Of > course, I don't have access to the barriers, so my viewer must be single > threaded. > > John Argentieri > > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
