Hi Roni, That checks against default were removed in a previous submission to resolve problems with setting method variables back to a default when they had been changed to another value other the default, so reverting it would break it. This is most problematic when using the serializers for reflection, but this problem can also happen if the serializer default value is different from the default constructor value for that parameter.
With the changes you made, they aren't a bug fix, as the code is correct, but the fact it looks a like a fix to your problem is down to it simply hiding the bug that still exists in your own code or elsehwere in the OSG. With the bug you are seeing we have to ask why not applying a default would address a problem, this sounds like a bug, but without having an example that reproduces the problem there is no way for me to know where the bug might be. Could you create a small example that illustrates the problem? Robert. On 4 June 2015 at 15:43, Roni Zanolli <[email protected]> wrote: > Hi Robert, > > I have attached the zipped file. This is version osg 3.3.7. In reality I just > add > a removed condition that was in the file in the version 3.3.1. > > if ( ParentType::_defaultValue!=value ) > > Removing that condition broke the option to save the hud camera when writing > the scene to a osgb file. > We have tested this on Linux and mac os x. > > osgDB/Serializer > > Thanks, > > Roni > > ------------------ > Read this topic online here: > http://forum.openscenegraph.org/viewtopic.php?p=63949#63949 > > > > > Attachments: > http://forum.openscenegraph.org//files/serializer_176.zip > > > _______________________________________________ > osg-submissions mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
