[osg-users] DEEP_COPY_USERDATA isn't that deep

Chris Djali krizdjali at gmail.com
Mon Sep 23 09:34:47 PDT 2019


Good, but would the new enum entry be for the current behaviour or the new behaviour? If the current behaviour is a bug, then it makes sense to only keep the old behaviour as the new enum value so everyone gets the fix, but conceivably there could be applications that rely on the current behaviour not changing, so would want the same name and value to keep the same behaviour.


Read this topic online here:

More information about the osg-users mailing list