The .osg file format is extensible via a plugin mechanism. See, for
example, osgdb_osgText.
In order for standard osgviewer to load a file that contains custom
callbacks, you will need to distribute a dynamic library containing
your custom callback class, and also a dynamic plugin to support .osg
I/O for your custom class, so two dynamic libraries total.
Paul Martz
Skew Matrix Software LLC
_http://www.skew-matrix.com_ <http://www.skew-matrix.com/>
+1 303 859 9466
Hi Paul, thx for your answer.
I was not talking about a custom Callback ( unless any Callback is
custom ). The Tutorial I was talking about is from your book, Listing 3-3.
By now I found out, that I need to use osgDB::writeObjectFile instead of
writeNodeFile, which writes "UpdateCallbacks{}" into an osg file.
The Node.cpp file from osgPlugins/osg/ has an output fw.writeObject
entry which takes the pointer to an UpdateCallback as argument.
I assume, that an UpdateCallback and derived knows what to write into
the osg file UpdateCallback code block.
Which method of an Object ( UpdateCallback ) fills this code block, and
how ?
The purpose is to write osg files for osgAnimation and osganimationviwer.
Peter Particle
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
