I'm not meaning to be rude or anything, but isn't that backward?
Shouldn't classes deriving from Referenced only be allocated with
"new", i.e. on the heap? the ref_ptr should not be allocated on the
heap unless it's a data member on another object that is allocated on
the heap.
On Jan 5, 2007, at 11:28 AM, Don Burns wrote:
Notwithstanding Robert's lovely comments and implications, you
should not be using anything deriving from either osg::Referenced
or Producer::Referenced on the heap. These objects should be
allocated on the stack. If the object is still not cleaning up
properly after using these objects on the stack, please let me know
the problem and I'll fix it.
-don
On 1/5/07, Argentieri, John-P63223 <[EMAIL PROTECTED]> wrote:
Robert and Gang,
I seem to remember you mentioning the use of a sceneview object
within an opengl app that has been setup without using a
rendersurface, using standard opengl techniques. Could anyone point
me in the right direction to an example of this technique? The
reason that I ask is that rendersurface's thread is giving me
troubles when I close a window in a multiple viewport/window setup.
Perhaps I can allocate the rendersurface on the stack? When I
allocate it on the heap, it's not cleaning up properly. Perhaps I
should be using Producer's ref_ptr object with it? I can't have
memory allocation continually increase as user creates and destroys
views.
Thanks for your input.. Your pal,
John
_______________________________________________
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/
