Attached patch updates the route-manager to use FGPositioned to search for waypoints, instead of a manual airport / fix / navaid search. This is good because it's now using the 'strictly closest' match, rather than arbitrarily picking a distant fix over a nearby navaid. In my case, the TLA VOR is significant to several EGPH procedures, but also happens to be the ident of a fix a long, long way away.

Also updates the FGPositioned class to stop using Point3D, partly because it's deprecated and partly because I had misunderstood the interface and was using it wrong. For now, all FGPositioned distance checks use SGGeodesy::inverse, which is accurate but inefficient. Once FGPositioned queries are used for something on a hot path, I'll probably store the cartesian position as well as the geodetic, to make these checks fast.

More route-manager changes to come - if you're using it regularly, and are aware of any issues (existing or caused by my patch) please let me know.

Regards,
James

Attachment: route-manager-search.patch
Description: Binary data




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Reply via email to