Hi guys, On 13/02/11 20:17 , PC John wrote: > void CameraManipulator::setHomePosition(const osg::Vec3d& eye, const > osg::Vec3d& center, const osg::Vec3d& up, bool autoComputeHomePosition=false) > > takes eye parameter as a position of the camera. >... > You may be interested to take a look at > void CameraManipulator::computeHomePosition(const osg::Camera *camera, bool > useBoundingBox)
I believe the actually issue that the original poster has is that not all CameraManipulators actually use these values. E.g. the SphericalManipulator uses the center but does it's own calculation for eye position, whereas the DriveManipulator uses all three. (From memory.) The individual behaviour is unfortunately not documented. Cheers, /ulrich >> my question concern setHomePosition of MatrixManipulator and subclasses. >> >> Parameters are quite explicite and in therory first one indicate position >> of camera, the seond parametre = target of camera ? Am i wrong... i surely >> forget some detail since : in practice, position and direction of camera >> do not corespond to the parameter given to that method . >> >> I read old topic and some source example. .. but results are sometimes so >> strange when changing the parameters values, that make me think i should >> konw some important thing or tip about this method .... _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
