On Wednesday, February 5, 2003, at 01:16 am, Jim Wilson wrote:
This is really cool! Looking through the changes I couldn't see...should thisThis was a two hour hack I did to learn a bit more of the code, it was fun to do, and the end result is quite nice. It could use some polish (rounding off some digits), and while performance seems okay I'm worried on 'big' nodes it might be a hit. I'm simply using the propertyNode's changeListener API, so presumable there are some nodes in the tree which are not firing their valueChanged() methods when they should be; I can look into this but I don't know if it'll be a case by case thing or a bug in on of the SGPropertyNode methods. (Or possible I do have a bug that causes some nodes not to update, hmm)
work with all properties? The orientation and position path data doesn't seem
to update realtime. I can see lots of ways this can be used for debugging.
Performance impact is minimal.
One thing I haven't done is use the childAdded/Remove callbacks on the ChangeListener to dynamically update the list (you have to change nodes and then change back to refresh the list). I think this is fairly low priority though. Suggestions for other things to make this more useful for testing / debugging welcome.
H&H
James
--
There is no such thing as a humble opinion.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
