I've just committed a large patch to the navradio code, which re- structures the code, with the aim of increasing the readability (and maintainability) significantly. This is in preparation for some other changes, especially making the 'NAV/GPS switch' function more explicit, and hopefully removing any knowledge of GPS-type systems from the nav-radio proper.
I've tested this locally for several days, but the code is full of conditionals - for GPS-coupled operation, ILS/LOC operation with and without glide-slopes, and many other similar things. Working on the basis that I will only encounter a subset of cases myself, I'm committing it with the promise to fix any problems that crop up ASAP. Note that some things which were subtly broken before, are now more obviously broken: notably GPS-slaved-glideslopes (which has a prior FIXME). Similarly, I've made no attempt to fix any particular behaviour of the code - if it behaved a certain way before, it should be exactly the same now, for better or worse! Regards, James ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
