> > That also has another implication. If you're making a camera manipulator > that needs to modify the projection matrix, then you need to put in some > other mechanism in your own code to get the projection matrix that the > manipulator would calculate to the camera. Because the only thing that will > happen automatically when using a camera manipulator is that > getInverseMatrix() will be called to get an updated view matrix each frame, > nothing will be done about the projection matrix at all. I've always found > that weird... A more general camera manipulator should have a mechanism to > alter any relevant property of the camera, not just the view matrix... It > could even have a pointer to the camera, which IMHO would have been a more > straightforward and clear design, at the cost of higher coupling. >
The class that manipulates the view matrix is a MatrixManipulator... Maybe it would be an elegant solution to just use another MatrixManipulator to manipulate the projection matrix...? Eduardo
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
