Curtis L. Olson writes: > 2) As you know, accessing property manager values via static > propertynode pointers is more efficient because you only have to do > the expensive string name hash lookup once the first time the routine > runs. It would be nice to have a set of static property node > accessors set up that any code could use, rather than having each > routine duplicate the static propertynode element it needs. Perhaps > it would make sense to put all these static accessors into FGInterface > and creat accessor functions for them? <stepping back out of swinging > distance> :-)
I thought of having protected convenience variables at the FGInterface level holding SGPropertyNodes for the information that every FDM absolutely *must* publish -- the three-member position, angular, velocity, and angular-velocity vectors. On the other hand, that introduces opacity; having *all* of the property nodes in the derived class mades the code easier to understand and maintain. > 3) And we'll need three very large folks to sit on Norman and hold > him down while we do this. :-) :-) :-) Send me a couple of good chocolate cake recipes -- I'm almost there. All the best, David -- David Megginson [EMAIL PROTECTED] _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
