flightgear

fly/flightgear

Fork 0

Commit graph

Author	SHA1	Message	Date
jmt	e171f0ecdb	Rename FGMarkerBeacon to FGMarkerBeacon record, to avoid a clash with the instrument of the same name. In the future I'd prefer to rename the instrument class instead (FGMarkerBeaconReciever?) but this is the safest change for now. Thanks (again) to Yon Uriarte for pointing out the problem (which seems to affect MSVC more than gcc)	2009-01-07 10:33:02 +01:00
jmt	d756f913ec	Refactor marker-beacons to be distinct from FGNavRecord. This is a big space saving for beacons, but since they're surprisingly few (in nav.dat), not a an enormous saving in real terms. The major motivation is that marker beacons don't behave like other NavRecords for radio interaction - they have no ident, frequency or range (in the sense that NavRecord means them).	2009-01-07 10:17:35 +01:00

Author

SHA1

Message

Date

jmt

e171f0ecdb

Rename FGMarkerBeacon to FGMarkerBeacon record, to avoid a clash with the

instrument of the same name. In the future I'd prefer to rename the
instrument class instead (FGMarkerBeaconReciever?) but this is the safest
change for now.

Thanks (again) to Yon Uriarte for pointing out the problem (which seems to
affect MSVC more than gcc)

2009-01-07 10:33:02 +01:00

jmt

d756f913ec

Refactor marker-beacons to be distinct from FGNavRecord. This is a big space

saving for beacons, but since they're surprisingly few (in nav.dat), not a
an enormous saving in real terms. The major motivation is that marker beacons
don't behave like other NavRecords for radio interaction - they have no ident,
frequency or range (in the sense that NavRecord means them).

2009-01-07 10:17:35 +01:00

2 commits