I was pondering this the other day and it occurred to me that the problem
boiled down to the fact that some (if not all) serializers do not write via a
subclass of NodeVisitor, and hence are unaffected by nodemasks.
I wondered if you could simply make your node so it is ONLY visible to
Robert Osfield wrote on 2011-09-05:
There isn't a scheme for missing nodes during serialization.
On Sat, Sep 3, 2011 at 12:01 PM, Joel Graff pair_o_gra...@comcast.net
wrote:
Hi,
I have a graph that I serialize with a simple call to
osgDB::writeNodeFile(), but it contains a node that is
On Sat, 2011-09-03 at 13:01 +0200, Joel Graff wrote:
Hi,
I have a graph that I serialize with a simple call to osgDB::writeNodeFile(),
but it contains a node that is auto-generated when the application starts.
Is there a way to exclude that node from serialization? I'm familiar with
Hi Joel,
There isn't a scheme for missing nodes during serialization.
Robert.
On Sat, Sep 3, 2011 at 12:01 PM, Joel Graff pair_o_gra...@comcast.net wrote:
Hi,
I have a graph that I serialize with a simple call to osgDB::writeNodeFile(),
but it contains a node that is auto-generated when
Hi,
I have a graph that I serialize with a simple call to osgDB::writeNodeFile(),
but it contains a node that is auto-generated when the application starts. Is
there a way to exclude that node from serialization? I'm familiar with the
setNodeMask() / setTraversalMask() mechanism used in
5 matches
Mail list logo