1
0
Fork 0
Commit graph

7 commits

Author SHA1 Message Date
curt
2caa017a79 Change nav->get_elev() to nav->get_elev_ft() to convey the actual units
explicitely.  This value has always been feet, but there were a couple places
in the code that assumed this elevation was meters.  The result was that you
could park directly over the top of the Black Forest VOR (112.50) NE of KCOS
and get a dme reading of 2.5 or so.  This problem is now resolved.
2004-03-14 23:01:09 +00:00
david
ac5a894711 Clamp a lower end on the range, for now. 2003-10-01 21:11:34 +00:00
ehofman
a6c1632298 Fix a small problem which crept in after a late night session 2003-04-01 08:36:09 +00:00
curt
d3f6354332 Return code to it's original form which works around an idiosyncracy in
our data.
2003-04-01 04:13:02 +00:00
curt
d25fa96db3 Previously if a freq search matched an ILS that had no dme, it would
proceed to search for an VOR of that same frequency.  On rare occasion
this search could return true with a far distant VOR and cause a small
amount of confusion.
2003-04-01 03:44:20 +00:00
david
f10f03fd43 Corrected some typos. 2003-03-10 14:09:26 +00:00
david
1f7e33b73d New version of basic DME support. This can coexist with the old one
for a little while, since it uses different properties.  There are
some improvements, especially with searching and range.  It also has
its own serviceable and in-range properties, independent of any
coupled VOR.
2003-03-09 03:20:34 +00:00