> -----Original Message----- > From: [email protected] [mailto:osg- > [email protected]] On Behalf Of Robert > Osfield > > I don't believe you have grasped what I'm suggesting about using > Camera post/final draw callback, rather than attaching and osg::Image > and then processing this with the callback, you manage everything > related to the allocation, image reading and post processing in the > callback - this way you have complete control over the whole post > process pipeline and can do as you wish.
I think I did grasp you suggestion, but what you suggest is exactly what I'm trying to avoid. Your suggestion will lead to something similar that osgscreencapture example does, and that is unnecessary osg::Camera code duplication. In this scenario one has to determine what was render target implementation and then derive propert tehnique for that. My point is that all the stuff is already provided by the camera implementation. All I suggest is some final customization step, something like read pixels callback would provide. > The Camera post/final draw callbacks offer you far more flexibility > than a Image::readPixels callback could ever do so I can't see any > point in the readPixels callback, and believe it's simply the wrong > way to tackle the problem you want to solve. > > Robert. Anyway, I agree that at this point it is best not to include this feature into core. Thanks for your suggestions and time spend... Robert M. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
