John Wojnaroski writes: > Boy, still trying to get my brain around this property stuff.
Do you have any 'specific' questions about the property manager? Basically it is a key / value hash with an increasingly variety of convenience functions. The nice thing is that the 'key' is an ascii string so it is a way to tie config file names to actual flightgear values at run time. This is wonderful for things like instrument panels which can mostly be built with text files and no coding or dlls or any of that sort of thing is required to create new instruments. It's also a handy way to loosely interface different sections of code together. Much of the 'percieved' complexity is in the convenience functions that ship with the property system. You can cache the pointer result of an ascii string lookup so it is done just once and not every iteration through the main loop. You can traverse the property tree like a unix file system. You can bind property names to actual C variables rather than just having the values live in the property manger space, they can instead live in the C code. You can load the contents of an xml file directly into a property subtree (quick way to load / save config files.) But really, the property manager is simply a key / value hash. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
