Hi Laurens, sorry if my point is not clear. My snippet works fine but if nobody does that (at least in the trunk) I may be missing some point. More generally, I am wondering why writing should be so different from reading.
I would like to be able to use recurive pseudo-writers just as we use recursive pseudo-loaders e.g. from https://github.com/openscenegraph/osg/blob/master/src/osgPlugins/trans/ReaderWriterTRANS.cpp#L141-148 Code: // recursively load the subfile. osg::Node *node = osgDB::readNodeFile( subFileName, options ); if( !node ) { // propagate the read failure upwards OSG_WARN << "Subfile \"" << subFileName << "\" could not be loaded" << std::endl; return ReadResult::FILE_NOT_HANDLED; } In this loading snippet, the plugin lookup is handled by osgDB transparently and I wonder if there is any good reason that writing doesn't work in a similar way. Regarding the return value, for consistency with osgDB::readNodeFile, osgDB::writeNodeFile should return an osg::Node* and we could add an osg::WriteResult(Object*, WriteStatus) constructor still for consistency. ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=60208#60208 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
