Hi Kim, META_Object and META_Node are just convenience macro's that help streamline the writing of subclasses, have a look at their definition to see what they do. The methods that these macros implement are useful for implementing IO and other ops that require richer RTTI info that C++ provides by default.
Robert. On Tue, Apr 8, 2008 at 1:11 PM, Kim C Bale <[EMAIL PROTECTED]> wrote: > Hi all, > > > > I've started to inherit from some of the core osg classes to modify their > functionality and I noticed the use of this META_Object definition in > headers. Now I traced this back to its definition in osg::Object and I just > wanted to clarify its use. > > > > To give a bit of background I am currently inheriting from > osgParticle::ParticleSystem in order to override it's update function. Am I > right in thinking that the META_Object call is just a convenience definition > that define the set of copy operations? If so, does it need to be included > in the classes I create that inherit from the osg library? > > > > Regards to you all, > > > > Kim. > > > ***************************************************************************************** > To view the terms under which this email is distributed, please go to > http://www.hull.ac.uk/legal/email_disclaimer.html > > ***************************************************************************************** > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > >
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
