[osg-users] DEEP_COPY_USERDATA isn't that deep

Robert Osfield robert.osfield at gmail.com
Fri Sep 20 22:59:00 PDT 2019

Hi Chris,

My guess is that the deep copy support wasn't built in when I wrote it.
Different parts of the OSG developed at different points so sometimes you
get little inconsistencies.  Feel free to modify the code to do a deep copy
when requested and generate a PR for it.


On Fri, 20 Sep 2019 at 19:54, Chris Djali <krizdjali at gmail.com> wrote:

> Hi,
> Is it intentional that using osg::CopyOp::DEEP_COPY_USERDATA copies the
> UserDataContainer, but doesn't deep-copy the actual things in it unless
> osg::CopyOp::DEEP_COPY_OBJECTS is also enabled? This means that things can
> be added or removed, but changes to existing things are shared.
> We have a situation where we only want to deep-copy the userdata and not
> anything else, so can't set the deep-copy objects flag. This could be
> supported either by ORing objects into the copy op in the userdata
> container copy constructor, or by adding another copy op for copying
> userdata even more deeply, otherwise we're going to have to manually
> implement a less pretty workaround.
> Cheers,
> Chris
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=76725#76725
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openscenegraph.org/pipermail/osg-users-openscenegraph.org/attachments/20190921/c1a72837/attachment.html>

More information about the osg-users mailing list