Hi Vincent, On Mon, Dec 15, 2008 at 8:31 PM, Vincent Bourdier <[email protected]> wrote: > The disturbing thing, is that the Dragger set the commandManager in a > pointer (dragger->setcommandManager ) so we can assume that the command > manager is well stored in memory... but no ! > Without the source and a good debuguer, I would not understand that.. > Vincent.
I'm rather busy with other tasks still so haven't looked into the details of this problem yet. Added a ref_ptr<> into Dragger would be OK as long as CommandManger doesn't keep references to the Draggers otherwise a circular dependency would be created. I really need to sit down with the design and see what would be the best thing, this might mean refactoring things inside osgManipulator so that there is no CommandManager, or it has a different role. osgWidget itself could become something that osgManipulator is based on, but this itself has some issues with application level objects needing to be constructed that perhaps could be avoided with some careful scene graph management. Unfortunately all this takes some quieten time of reflection to sort out improvements design, something I don't have the luxury of right now. After 2.8 hopefully there will be a slot where I can sit back a spend a few days on this stuff. For 2.8 we'll just need to spot short term fixes like introducing a ref_ptr<> to avoid CommandManager going out of scope while still being used. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
