HI Andrew, The use of virtual inheritance enables you to create a callback that inherits from a DrawCallback and and other callbacks without having issues with reference counting. Multiple inheritance in this context is being used to define multiple implemented interfaces.
Why this is causing compile problems for you is not something I can answer, it's valid C++ and is something that is compiled all the time across all platforms, including Windows. Many of the OSG callbacks also use virtual inheritance in this way. To find out why you are getting problems while others don't we will need to dig deeper into the specifics on what you are doing at your end. It could be a bug in VS, it could be a build error in some way. To help others help you you'll need to explain which version of the OSG you are building with, the OS version + service packs, the service packs you've applied to VS, when in the build you see the error. Robert. On Wed, Jun 10, 2009 at 5:36 PM, Andrew Cunningham<[email protected]> wrote: > Ok I found what the problem is caused by .... > > To me it looks like a typo in the "camera" header file... > > struct OSG_EXPORT DrawCallback : virtual public Object > > I can't imagine any reason to make Object a "virtual base class" here. > > struct OSG_EXPORT DrawCallback : public Object > > Changing this and rebuilding the osg libraries caused the link error to go > away. > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=13857#13857 > > > > > > _______________________________________________ > 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
