Hi Tony, Spend some time with OSG code, you'll find it far more flexible than anything that Performer had. It's investing time into learning the OSG rather than just working out how to do something equivalent to Performer because your original design may well have been compromised by the limitations of Perfomer, with the OSG it is extensible so you mold it to how you want to work rather than moulding how you work to fit limitations in front of you.
Robert. On 10 September 2015 at 08:46, Tony Vasile <[email protected]> wrote: > Hi Nick & Robert, > That's not quite the same functionality as it appears that in Performer > there is some sort of memory/map that is used to map a user defined name as > a string to a slot number. You then add data to the node using this slot > number. Performer does have a call to setUserData which takes the data as > its argument but it installs the data in slot 0. There is another > setUserData that takes two argument, with the first argument being a slot > number. I assume that getNamedUserDataSlot is just an allocation scheme > between the string name and and a magic number which represents the slot. > > That's cool this sort of functionality I could easily replicated with a > couple of maps or a vector. > > Thanks for your help. > > ------------------------ > Tony V > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=65089#65089 > > > > > > _______________________________________________ > 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
