Hi Steve, osgviewer already supports -p path, but osgViewer::Viewer itself does do this automatically - this is something that the application needs to parse and wire up. See the applications/osgviewer/osgviewer.cpp example.
Support for ascii configuration files is not yet complete. I've not part of this work, and when I get a opportunity will add this. W.r.t DISPLAY reading, this wasn't support in 2.0, but is now read in 2.1.x and SVN version. The reading of DISPLAY is done in the View::setUpView*() methods. Feedback from the community suggested it was working fine. Robert. On 9/11/07, Steve Nash <[EMAIL PROTECTED]> wrote: > I have a question about the functionality of the osgviewer example > functionality with OSG 2.0+. I see at > http://www.openscenegraph.org/projects/osg/wiki/Community/Tasks/osgViewer > that there is plans to support ASCII configuration files. Does this > include both the camera config file and reading flight path files (-c > and -p respectively with pre OSG 2.0 osgviewers)? > > Additionally, it seems the new osgviewer isn't honoring the $DISPLAY env. > variable. > It seems to always use :0.0, in spite of what $DISPLAY is set to (I also tried > using OSG_SCREEN, which resulted in use of :0.$OSG_SCREEN). I built both 2.0 > and 2.1.9 on RHEL4U3, with the same results. > > Sorry if this has been hashed out elsewhere, but I couldn't find it in the > archives. > > Thanks, > Steve > _______________________________________________ > 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
