Torsten Dreyer wrote: > > > I believe that the correct behaviour is as follows: > > > > > > Decrementing 126.00 results in 126.97 > > > Incrementing 126.97results in 126.00 > > > > Are you sure? I believe the curren behaviour is correct but not for sure > > ;-) I check it out within the next few days and drop a line here (probably > > not before the weekend). > Hi Stuart > > I owe you a reply - sorry for keeping you on hold for so long.
No problem - I've been very busy myself.
> I have verified that the behaviour you described is correct: wrapping around
> the kHz does not change the MHz. I tested a KX165 and a KX155.
> Would you mind posting the intended patch for the kx165, so I can give it a
> try?
>
> Thanks, Torsten
The patch is attached.
Note that you'll need to include tune.nas in the aircraft -set.xml file, as
described
in the README.txt, though just dropping it into data/Nasal might work (I haven't
checked).
Assuming that we want to use this, I'm not sure whether tune.nas should be in
Aircraft/Generic, or data/Nasal.
Melchior - do you have an opinion on this (ignoring for the moment the
indentation
which I will fix before commit) ?
-Stuart
tune.tgz
Description: application/compressed-tar
------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
