(Sorry for messing up with the references, I forgot I could not post
via gmane and had to subscribe first)

I'd like to confirm that behaviour.
Knowing nothing about prior versions, I think the ultimate reason can
be found in l. 304 and 306 of KNS80.nas:
When dme-hold gets set it wouldn't do the right thing as some error occurs:
Nasal runtime error: props.setDoubleValue() with non-number
So the dme instrument will subsequently be in an improper state and
thus in-range will be false/nil.

While a .setValue(...) would correct this in l. 304, I think l. 306
isn't really needed at all. If commented out, that branch works as
expected too.

I looked at the whole stuff a few days ago and found that even then it
wouldn't work as described in the KNS80 Pilot's Guide (see #16 p.
18f). I messed around with it, but being new to nasal hacking I
produced a horrible spaghetti-like code, which does work in mode 0 but
not entirely as described in the other ones. So I felt I cannot offer
that to Syd yet, whom I'd like to thank for the great work he is
doing.

regards
Klaus Hoercher

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Flightgear-users mailing list
Flightgear-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-users

Reply via email to