Hi Robert, Chris, Paul,
On 1/12/09 10:45 AM, Robert Osfield wrote:
The existing style UserData and Descriptions could be stored in the
exactly the same way as they are now, only shifted into the
CompositeUserData structure. The additional new key based stored
could be added alongside these.
This sounds like a good solution, it keeps API compatibility but only stores one object
instead of _userData/_descriptions in every Object/Node created.
And the getters/setters would divert the call to the CompositeUserData instead,
right?
This would work nicely for my problem of attaching image specific data to osg::Image in
the loader (as long as CompositeUserData provides some sort of key/value storage).
As mentioned earlier osgDB::Options (derived from osg::Object) has getters/setters for
PluginData as well. I imagine these could use the same mechanism as well? And
getOptionString() too?
So many birds with one stone :-)
Cheers,
/ulrich
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
