Melchior FRANZ wrote: > For example, the removed "x" value on second display is read again:
Both of those circumstances have a default value specified, for precicely the reason that the nodes may not exist. Calling getIntValue(node, default) on a node that had previously been deleted with removeChild() should *never* return anything but the default value specified (that is, after all, the whole point of having a default value in the first place). That sounds like the bug, not the dialog code. Andy _______________________________________________ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
