Hi John, I feel that keeping the singleton style functions is a bit less intrusive and flexible in case we want to make changes in the future so I have kept these functions, but moved the actual static variables into the global scope. This change is now checked into svn/trunk. Could you test this to make sure my changes work fine.
Cheers, Robert. On 12 March 2012 12:23, PC John <[email protected]> wrote: > Hi Robert, > > this is a fix for the issue discussed on osg-users today. > Apart from moving s_sceneCacheMutex and > s_sceneCache to global space, I removed nearly-empty getSceneCache() and > getSceneCacheMutex() and replaced them by variables. It works perfectly for > me. Feel free to adjust whatever. > > John > > ---------- Forwarded Message ---------- > > Subject: Re: [osg-users] Scene.cpp deadlock > Date: Monday 12 of March 2012, 11:54:31 > From: Robert Osfield <[email protected]> > To: OpenSceneGraph Users <[email protected]> > > On 12 March 2012 11:19, PC John <[email protected]> wrote: >> Do you think moving static s_sceneCacheMutex and >> s_sceneCache of Scene.cpp into the global scope would be the proper fix? > > Yes I think it'll be the least intrusive way to fix the issue. Could > you try it and see if it works fine, if so just post me the changes. > > Cheers, > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org > ----------------------------------------- > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org > _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
