> John,
>
> Ok, I have committed these changes. Thanks. Please note that simply
> uncommenting accessors in flight.hxx won't necessarily make that data
> available and valid. The various FDM's would need to fill in the
> values and if they don't, then the data won't be valid.
>
Understand.
Being a positive person, I just know the FDM developers will want to get it
right and I want to be ready. :-)
Betting on the come. if it's not correct or valid I can just ignore it then
on the opengc side or derive a "replacement" value
Boy, still trying to get my brain around this property stuff.
BTW: I've reworked the navigation stuff to fit more into what an FMC does
(like displaying ALL fixes within a
specified range, moving map stuff, weather/airport overlays, multiple DMEs,
etc) I've made a major change in the way the search is conducted. Since I
don't fully understand the history or background as to why
navaids/radiostack is the way it is, my approach could be all wet, but I'll
forward it (probabaly best after the 0.7.9 release) for comments. If it
makes sense, I'll be happy to work it back into FG as appropriate. As the
models keep improving toward higher performance twins, the avionics will
have to grow as well. So it might be right inline....
Stay sane.
Regards
John W.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
