Hi Robert,

The root of the problem that currently OSG is just one of two SceneGraphs in the system. We are currently in the process of migrating to OSG and as soon as the migration is complete I am confident that this issue will be resolved. However, in the mean while we have to keep backwards compatibility with the old scenegraph for a transitional period. It's a strain, but also a necessity.

Best regards,
John

Robert Osfield wrote:
Hi John,

On Mon, Sep 22, 2008 at 9:29 AM, John Vidar Larring
<[EMAIL PROTECTED]> wrote:
If I remember correctly from the call stack: the call to
osg::getGLVersionNumber() was prompted by
osgViewer::GraphicsWindowEmbedded's d'tor with several other calls
stacked in between.

My best guess would that the destructor was trying to clean up OpenGL
objects associated with that context.  If you did no rendering then
the OSG shouldn't have created any objects so you might be safe... but
I would wonder if not other OpenGL calls will be made.   Personally I
would not feel like this problem is solved, there may well me a crash
just waiting to catch you out.

Robert.
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org



--
Best regards,
John
WeatherOne


--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

Reply via email to