You are right about this. I would welcome more as attribute support though (like descriptions is implemented. There was some discussion abiyt having attributes in the nodes I remember, but sure if it is implemented.
-Nick On Wed, Jun 30, 2010 at 1:27 PM, Sebastian Messerschmidt < [email protected]> wrote: > Hi, > > Some file formats like OpenFlight can contain various data, which might not > be directly related to rendering but can be important in other contexts. > While I fully agree that the loaders can and should skip this information > when constructing the scene-graph, I would find it extremly useful to have > some callback mechanism for those skipped entities. > > @Robert: > Can you think of a general concept that could be integrated into the > loader-infrastructure? My idea was to use a callback mechanism that can be > installed and registered to the loader implementation. Those callbacks would > textually tell me what kind of non-render-related data was read for which > node/geom etc. > > For instance flt can contain things like surface material codes and > featured ids. I imagine having a callback functions like this: > > class LoadCallback > { > > > virtual void customData(const std::string& element_data, osg::Node& node, > int data) > > virtual void customData(const std::string& element_data, osg::Node& node, > float data) > > ... various overloads > > } > > > Those could be called inside the loader: > > > ... > _loadcallback.customData("OpenFlight::SMC", current_node, readuint(16)) > ... > > > Do you think that such extension would be general enough to be applied to > loaders? Would you mind If I try to include such concept? > > cheers > Sebastian > > > > _______________________________________________ > 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
