Robert, Thanks for the hints on the closing of the window. When I get sometime I will go in and play with the closing and see if I can get rid of the crashes. I will also look at the composite viewer and see how to implement it into the MFC framework. This should be very minor I just need to find sometime to work it. Thanks, Mike
________________________________ From: [EMAIL PROTECTED] on behalf of Robert Osfield Sent: Mon 5/28/2007 9:45 AM To: osg users Subject: Re: [osg-users] about the osgViewerMFC example Hi Mike & Miguel, First up the PFB_DOUBLEBUFFER was fixed by Mike last week, so is part of the 1.9.6 release. Second up, not sure why the optimizer might fail. I haven't used this example at all (I work under Linux), in general the optimizer does crash. Thirdly, this is a note for Mike, the threads on exit should clean themselves up automatically, but... if the graphics context is deleted before viewer threads are stopped then it could cause problems that the viewer can't do anything about. On close windows you should see if you can defer the window close to the viewer to handle. Alternatively call stopThreading on the viewer on the windows. Finally I have to add this example is really an example that would probably be best done using CompositeViewer with each new window a separate View rather than a separate Viewer. Robert. On 5/28/07, Hartman, Michael W. (MSFC-NNM06AA05Z)[PEOPLETEC] <[EMAIL PROTECTED]> wrote: > Not sure why the optimizer crashed but with the second issue I had the same > problem on my home computer and found that the pixel description needed to > have PFD_DOUBLEBUFFER defined. Once I added this I was able to see the > object but without it all I had was a blue background for the window. Please > check to make sure that your pixel description has this defined (located in > the MFC_OSG.cpp file). I know that the latest subversion contains this > change. > > As for the last issue; I have also seen this (on my home pc, it is > intermittent) and believe it is a threading issue (trying to close the window > before all threads have exited) and I don't have much experience with > threading so I would have to rely on the community to get into the code and > figure out how to fix the issue. > > Thanks, > Mike > > ________________________________ > > From: [EMAIL PROTECTED] on behalf of Miguel Martinez > Sent: Mon 5/28/2007 3:49 AM > To: osg users > Subject: [osg-users] about the osgViewerMFC example > > > > Hi all, > > I have the 1.9.5 OSG release, and testing the osgViewerMFC example I > have found several problems: > > - When loading a model, optimizer.optimize crashes > - When I comment this line, the program runs correctly but when I load a > file, I dont see the model, just an empty scene. > - When I close the app, the program crashes in CMDIChildwindow::MDIDestroy() > > I'm using VC.NET 2003. > Am I the only one with this problem ? Am I doing something wrong ? > Can someone post another more stable example using MFC's ? > > thanks ! > > // Miguel Martinez > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > > > > _______________________________________________ > osg-users mailing list > [email protected] > http://openscenegraph.net/mailman/listinfo/osg-users > http://www.openscenegraph.org/ > > _______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
<<winmail.dat>>
_______________________________________________ osg-users mailing list [email protected] http://openscenegraph.net/mailman/listinfo/osg-users http://www.openscenegraph.org/
