> This change wouldn't be a clone() method, it'd be a > shareASingleClone() method which is a totally different thing and in the general case > would not be safe or appropriate a replacement for clone().
Maybe I explained it incorrectly, the idea is simply that calling clone should give you an exact clone of the argument, with all the relationships between its child nodes intact. But I accept that it's a big change, I'm glad I checked with you before I started relying on it :) As it stands, osgAnimation is compatible with cloning as it is: relationships between nodes are inferred from their names. Issues with COLLADA using non-unique IDs prompted me to suggest setting pointers to identify related objects, but I can work around it another way. Thanks for your quick response -Michael _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or g ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ ______________________________________________________________________ This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________ _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
