Jim Wilson wrote:

For the sound code I implemented two <internal> properties which reflect the time elapsed since starting the sound, and the time elapsed after stopping the sound.

This could be useful for the model animation also.

A countdown timer class with a writable property tree node would be useful and easy to do (e.g. timer.value =- dt).

Yes, bat that would overwhelm the property tree. The <internal> timer properties are on a per event base. So every event should get it's own place in the property tree.


Erik



_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to