Hi Vijeesh, not the slot mechanism itself push the values into the visual_objects (I think the cigi name is "entity"), but every visual_object has an attached updater class. This updater class is executed during the OSG update traversal, and it pulls the values it requires from the slot mechanism.
I chose that "pulling" design to make it more flexible. In that case every object with it's updater has to manage it's data aquisition on its own (by subclassing of the updater class), the only common part every object has is that they retrieve there data from the central data management module - from the slots. In a "pushing" design, the central data management module would have to be aware of all used object types to be able to update it. This makes it more difficult to add additional object types. Any thoughts/ideas related to the data design? For deeper understanding of the current object design and data flow, please read this wiki pages: http://www.osgvisual.org/projects/osgvisual/wiki/visual_dataIO http://www.osgvisual.org/projects/osgvisual/wiki/visual_object Cheers, Torben ------------------ Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=38059#38059 _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
