Jon Berndt wrote:
> Can anyone differentiate for me the concept of "position" as
> contrasted to "index" in this situation?
Position is arbitrary. I think it corresponds to the order of which
the nodes were added to the parent. The only use I can think of for
this method is enumerating over all properties, as in:
for(int i=0; i<node->nChildren(); i++)
doWhatever(node->getChild(i));
Note that index is not always contiguous. It is perfectly legal to
have a node with 4 children, which have indices 0, 7, 21 and 123, for
instance.
Andy
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
