Re: [osg-users] memory allocation during updateCallback

2010-06-28 Thread Andre Simoes
Hello Ulrich. My main_child ref pointer is just a backup of the last group added for easy access. I never do something like addChild( main_child.get() ) out of this scope. I understand and will apply the programming practices you've suggested me to do inside the update. Do the UpdateCallback

Re: [osg-users] memory allocation during updateCallback

2010-06-25 Thread Ulrich Hertlein
Hi Andre, On 25/06/10 1:06 , Andre Simoes wrote: I've made a main osg::Group with an osg::NodeCallback attached to call some stuff each update. inside my osg::NodeCallback i have: void MyCallback:: operator()( osg::Node* node, osg::NodeVisitor* nv) { Frame *frame = (Frame*)node;

[osg-users] memory allocation during updateCallback

2010-06-24 Thread Andre Simoes
Hi for all. I've made a main osg::Group with an osg::NodeCallback attached to call some stuff each update. inside my osg::NodeCallback i have: void MyCallback:: operator()( osg::Node* node, osg::NodeVisitor* nv) { Frame *frame = (Frame*)node; if( ! frame-main_child ) {