I munged the code so that the routines that manage the "fix" database (waypoints etc.) and the "navaid" database are now insensitive to the upper-case / lower-case distinction.
That is, the "RBX" VOR/DME is now equivalent to the "rbx" VOR/DME. I have checked that all navaids and waypoints in the existing database were already monocase, so this will not create any new collisions. And even if it did, I think the new semantics would be preferable anyway. This lowers pilot workload, and eliminates a whole category of errors. This required editing four lines of code. C++ supports this sort of thing very nicely; it's the third argument to the map template. This is now incorporated in the patches at http://www.av8n.com/fly/fgfs/nearest-fix.diff and you will need to add the comparison function to the package somehow: http://www.av8n.com/fly/fgfs/strx.hxx There are actually three databases, namely 1) the "fix" database (waypoints etc.) and 2) the "navaid" database 3) The "runways" database (i.e. airports) and I have *not* gotten around to case-insensitizing the runway identifiers ("11r") or airport names ("ksfo"). ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
