[osg-users] Changing Renderer destructor from private to protected

[Mike Wittman]

Hi Jason,

 

A protected destructor is a valid solution if Robert's OK with it.  The
only other option I'm aware of is to suppress wrapper generation for
that type in the configuration for the code generator.
osgTerrain::GeometryTechnique is suppressed for that reason, for
example.

 

 

Mike Wittman

mwittman at seismicmicro.com <mailto:mwittman at seismicmicro.com> 

___________________________________________________

Seismic Micro-Technology, Inc.

8584 Katy Freeway, Suite 400 / Houston, Texas 77024

Tel.  +1 (713) 464-6188

Fax. +1 (713) 464-6440

Web:  www.seismicmicro.com
<blocked::blocked::http://www.seismicmicro.com> 

___________________________________________________

Seismic through Simulation with KINGDOM, (RC)2, and SURE! - CONTACT US
TODAY for more information.

 

________________________________

From: osg-users-bounces at lists.openscenegraph.org
[mailto:osg-users-bounces at lists.openscenegraph.org] On Behalf Of Jason
Beverage
Sent: Friday, August 24, 2007 4:00 PM
To: osg users
Subject: [osg-users] Changing Renderer destructor from private to
protected

 

Hi Robert and Mike Wittman,

 

I tried to build the osgDotNet wrappers last night against the latest
SVN and could compile them wrappers because osgDotNet subclasses
Renderer and tries to access its destructor, which is private.  I
modified Renderer to have a protected destructor and things built fine. 

 

Any issue with changing the access level of Renderer's destructor from
private to public?

 

Thanks,

 

Jason

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20070824/af04b3e6/attachment.htm