Andy Ross writes: > Sure, there's a print() function which uses SG_LOG; for exactly this > purpose. There's even a fancy dump() method on a property node that > you can use to dump a property tree to the console.
Ok, thanks, I eventually found it. Quite useful, thanks. :-) > It turns out to be a missing feature in the C++ code. The > Node.getChild() function worked for the getChild(name) variant, but > silently ignored the second argument for a getChild(name, index). I > just forgot to write it, apparently. :) > > An additional issue was that the number of /sim/selected/engines[n] > properties (one) in the default configuration didn't match the > actual number of engines, so engine 2 would always look > "unselected". I fixed this via a Nasal hack that patches things up > after initialization, but we should consider unifying these trees > somehow (for example, by putting the selected properties under > /controls/engines). I will vote for moving this into the tree with the engine controls. That should make the code a bit simpler. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
