On 5/15/07, belthil <[EMAIL PROTECTED]> wrote:
I want to precise that the problem when exiting the application is because of the fact the application does not succeed in finding the plugin to read the .jpg. When i comment the reading of the .jpg, that error does not happen anymore. But i still do not know how to resolve the problem of the plugin and the one of the buttons like "s" or "f" that do not work anymore...
The plugins work in exactly the same way between 1.2 and 1.9.x, and actuall between 0.9.x and 1.9.x. Any problem with not finding the image plugin is down to it not being built for some reason, or the plugin isn't on your path. Use the env var OSG_NOTIFY_LEVEL set to DEBUG to get verbose output of where the OSG is search for files and plugins. W.r.t 's' and 'f' keys not working, this is simply because osgViewer::Viewer doesn't include any manipulators by default (save for a fallback to TrackballManipulator if you call run without assigning a camera manipulator). To add the extra viewer functionality you event event handlers one by one for each bit of functionality. See the osgviewer examples source code. This incremental approach constrats the osgProducer::Viewer which is actually an "everything an the kitchen sink" viewer class, and as such it constrained the usage, and you had to learn how to switch things off, to get things pared down to what you actually needed. The osgProducer::Viewer might be better called DemoViewer class is this is what ended up dictating the functionality that got piled into it. osgViewer::Viewer is fresh start, its designed and implemented more as a general purpose viewer class. If you look at the API (note its subclasses from osgViewer::View so look here as well) and you'll find that its API is sparser, with much less implicit functionality hidden away. Robert. Robert. _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
