Hi OpenSG-Team, I've some question to OSG::Geometry fields (like e.g. positions, normals, etc) in OpenSG 1.8. In particular what happens when changing their capacity combined with thread synchronization?
The size of such a positions field (and all others) decreases and increases during runtime in my application. So I tried the shrink() function to get rid of some reserved memory overhead. But this only works for the thread from which the function is called, because during thread synchronization (applyChangeList()) a simple copy assignment is made. The workaround I've found is to create a new GeoPositions3f each time I decrease the size of positions. Is this an appropriate solution? Which drawbacks does it have? Additionally it seems to me that there are always copies of these fields for both aspects. If that's the case it would mean a big overhead. Is this true? I thought before that the data is not copied until beginEditCP() is called. Does OpenSG 2.0 cope with these issues in a different way? best regards Lars ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Opensg-users mailing list Opensg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensg-users
