Hi Lenny, I have refactored the OverlayNode usage of OverlayData, so that it's now possible to subclass OverlayData as it now uses a ref_ptr<> rather than an OveralyData directly, and the getOverlayData and OverlayData struct are now in protected rather than private space.
This change did screw up the wrappers, it took me while to workaround this, but it now it compiling. Moving to the svn trunk will get you this change. Robert. On Wed, Jul 23, 2008 at 1:54 PM, Lenny F. Halseth <[EMAIL PROTECTED]> wrote: > Hey, > > That is indeed the issue. It appears that each of the members that we > used to access have been moved into the private struct OverlayData, > which only has private access. The getOverlayData(...) function looked > almost like a solution, but, it too is private. > > As for the useage, I am not completely sure the purpose. This section > of code hasn't been anything I have worked with. This derived class is > used in conjunction with another class (a class derived from Delta3Ds > drawables). The traverse function was overwritten - with an edited > version of OverlayNode's. > > The node appears to be there for adding extra specific operations for > this section of the project, such as quickly hiding or showing what we > want by acting upon the nodes. The system itself is providing a minimap > for our scene (an overview that resides in a corner that displays the > whole map + extra information such as where objects are. > > I am trying to find out why this class was needed, as opposed to just > using an OverlayNode and moving the extra functionality somewhere else. > In the meantime, the easiest solution would of course just to somehow > get access from within the derived class. > > -Lenny > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Robert > Osfield > Sent: Tuesday, July 22, 2008 12:06 PM > To: OpenSceneGraph Users > Subject: Re: [osg-users] OverlayNode > > Hi Lenny, > > Is it the use of a private: section in osgSim::OverlayNode that is the > issue? > > I probably made this change to prevent problems with wrapper generation, > other than this then isn't a strong need to keep these protected. > > Could you explain what you are trying to do, and how you are going about > it. > > Robert. > > On Tue, Jul 22, 2008 at 4:37 PM, Lenny F. Halseth <[EMAIL PROTECTED]> > wrote: >> Hello, >> >> I have recently begun an upgrade process that involves OSG. The >> project I am on makes use of Delta3D, which makes heavy use of OSG. >> >> In a previous version, we derived a class from OverlayNode for our own > >> purposes. However, with the recent version of OSG, some of the >> members accessed do not appear to be accessible. Most of the things >> touched are now contained in the OverlayData structure. The class >> touches _texture, _texgenNode, _texture, _textureFrustrum, >> _mainSubraphStateSet, which now results in an error from not being > able to access. >> >> How should I go about gaining access to these, or, what should I >> consider for an alternative to deriving from OverlayNode? >> >> -Lenny >> _______________________________________________ >> 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.or > g > _______________________________________________ > 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
