Forgot to add, I am using the latest CVS and have no probs with memory leaks!
Its probably that your code is taken from the MFC example and that does produce memory leaks which I have looked at and could not quite grasp why. Its something to do with the debugger in VS2008 but cant put my finger on it at the moment, if i remember correctly its probably something to do with closing/creating the windows and where the OSG viewer? Is declared. Cannot remember if I came to the conclusion that it was the Visual Studio debugger and MFC... But my code don't leak(touch wood), so might be worth giving a go if you are not using the MFC classes. Regards Martin. From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of lalialter-ra...@yahoo.gr Sent: 09 April 2010 13:39 To: osg-users@lists.openscenegraph.org Subject: [osg-users] GraphicsWindowWin32 instead of Producer Is it possible to use osgViewer::GraphicsWindowWin32 (like producer) with osgUtil::SceneView in order to to makeCurrent or releaseCurrent context and do the update, cull, draw etc in it?? I've develop something like that but considering your high recommendation on using osgViewer instead of osgUtil::SceneView i have some second thoughts. Al thought it seems to work fine in my current release 2.2.0 but I have just some problems with texturing. Textures are disappearing on sceneView recreation. I searched the forum about a solution and your advise was to update on latest version. The problem is that updating on final osg release 2.9.8 there appears a lot of memory leaks. __________________________________________________ Χρησιμοποιείτε Yahoo!; Βαρεθήκατε τα ενοχλητικά μηνύματα (spam); Το Yahoo! Mail διαθέτει την καλύτερη δυνατή προστασία κατά των ενοχλητικών μηνυμάτων http://mail.yahoo.gr
_______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
