mirror of
https://github.com/OpenSquawk/OpenSquawk
synced 2026-07-31 22:05:34 +08:00
d9bc4fcbd9
The radio only ever held one airport's frequencies, loaded once at the start, so on a departure the destination's Tower never appeared however close you got — there was no way to dial ahead. Both ends of the flight are now listed: the field being flown first and unlabelled, the far end after it, tagged with its ICAO and drawn with a dashed border so it reads as somewhere else. The destination's stations are kept in their own list rather than merged into the primary one, because everything that resolves *which frequency this phase expects* — the frequency map, the expected frequency, the wrong-frequency gate, the ATIS wiring — reads that list, and folding a second airport's Tower into it would let the gate accept the wrong field's frequency. Out-of-range stations are dimmed rather than removed: VHF is line-of-sight, so a station unreachable on the ground is workable from the cruise, and it should come back as you climb. The distances come from the backend, which already derives them and now returns them — the browser does not need its own copy of the airport coordinates for this. With no bridge connected, nothing is dimmed at all. That is the normal case for someone practising without a simulator, and a station that cannot be *proven* out of range must not be taken away.