fly/flightgear
1
0
Fork 0
Code Activity
flightgear/src/Navaids/markerbeacon.hxx

43 lines
1.2 KiB
C++
Raw Normal View History

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-03 15:54:03 +00:00
// markerbeacon.hxx -- marker beacon class
//
// Written by James Turner, started December 2008.
//
// Copyright (C) 2008 Curtis L. Olson - http://www.flightgear.org/~curt
//
// This program is free software; you can redistribute it and/or
// modify it under the terms of the GNU General Public License as
// published by the Free Software Foundation; either version 2 of the
// License, or (at your option) any later version.
//
// This program is distributed in the hope that it will be useful, but
// WITHOUT ANY WARRANTY; without even the implied warranty of
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
// General Public License for more details.
//
// You should have received a copy of the GNU General Public License
// along with this program; if not, write to the Free Software
// Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
//
// $Id$
#ifndef _FG_MARKERBEACON_HXX
#define _FG_MARKERBEACON_HXX
#include <simgear/compiler.h>
#include "positioned.hxx"
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-04 20:12:43 +00:00
class FGMarkerBeaconRecord : public FGPositioned
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-03 15:54:03 +00:00
{
public:
Implement a persistent cache for navigation data. Cache the parsed navigation and airport data in a binary file to reduce startup times and memory consumption (since only referenced FGPositioned elements are held in memory). Data will be reimported when the mod-time of any input file is changed. If a global file is changed (nav.dat, awy.dat, apt.dat, etc), the cache will be completely rebuilt, which takes approximately 30 seconds on moderate hardware. (Future work may reduce this).
2012-08-27 23:26:36 +00:00
FGMarkerBeaconRecord(PositionedID aGuid, Type aTy, PositionedID aRunway, const SGGeod& aPos);
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-03 15:54:03 +00:00
private:
Implement a persistent cache for navigation data. Cache the parsed navigation and airport data in a binary file to reduce startup times and memory consumption (since only referenced FGPositioned elements are held in memory). Data will be reimported when the mod-time of any input file is changed. If a global file is changed (nav.dat, awy.dat, apt.dat, etc), the cache will be completely rebuilt, which takes approximately 30 seconds on moderate hardware. (Future work may reduce this).
2012-08-27 23:26:36 +00:00
PositionedID _runway;
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-03 15:54:03 +00:00
};
#endif // _FG_MARKERBEACON_HXX
Copy permalink