> > A couple of approaches have been suggested, and one stopgap (replace > > the ATIS data file with one that includes AWOS/ASOS like the one I > > generated[1]). Are any of these something we could pull into at least > > the plib branch? > > Why push for a stopgap solution? > > Code to do this has been in the Sport Model for eons.
As a user, I don't much care, as long as AWOS/ASOS is in there. I must leave it up to the developers to pick which approach suits them best - the one in your Sport branch is a possibility, my stopgap is a possibility, and no doubt there are other possibilities also. Seeing as the next plib release is, in some ways, a stopgap in and of itself I think it wouldn't be too bad to go with the stopgap for this release and do the right thing on the OSG branch. As for maintenance, the default.atis file is updated very infrequently AFAICT. Cheers ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
