I'd like to encourage everyone to put properties where they would
belong in real life -- I took a look at the properties for the nav
radio, and they gave me a bit of a headache.
Think of what a nav radio and indicator do and don't know in real life:
Does know:
- what frequency is tuned in on
On 20 Mar 2010, at 21:05, David Megginson wrote:
I understand that these properties are convenient for other systems,
but they should go somewhere they would be in real life, like a DME,
GPS database or FMS, not in the (relatively dumb) nav radio itself
under /instrumentation/nav/.
Yep,
2 matches
Mail list logo
