Andy Ross wrote:
Curt wrote:
FWIW, testing against "" instead of 0 works with the latest nasal
changes.
Indeed. Actually, with the fix as of a few minutes ago you should be
able to do just:
if ( !auto.getValue() ) { ... }
The empty string and zero numeric values are both false, as is the n
Curt wrote:
> FWIW, testing against "" instead of 0 works with the latest nasal
> changes.
Indeed. Actually, with the fix as of a few minutes ago you should be
able to do just:
if ( !auto.getValue() ) { ... }
The empty string and zero numeric values are both false, as is the nil
reference.
And
Curt wrote:
> It looks like /autopilot/locks/speed is a string field. It appears
> that "" no longer equals 0. My assumption when I wrote the script
> (hehe, I think I wrote that script, apologies to whoever if I
> didn't) was that for the comparison with zero, auto.getValue() would
> be converte
Curtis L. Olson wrote:
Andy Ross wrote:
I kinda doubt it. The bugs that were fixed were about string constant
conversion and not runtime behavior, and were pretty obviously wrong.
It would be pretty pathological to have code that actually depended on
that behavior.
The bug was that string constant
Andy Ross wrote:
I kinda doubt it. The bugs that were fixed were about string constant
conversion and not runtime behavior, and were pretty obviously wrong.
It would be pretty pathological to have code that actually depended on
that behavior.
The bug was that string constants (e.g. "1.2") could be
Curtis L. Olson wrote:
> Hmmm, for myself (linux) these things were working correctly until
> just very recently (the last week or few days.) I wonder if the
> changes to Nasal surrounding it's concept of 0 vs. false has broken
> portions of the script in controls.nas?
I kinda doubt it. The bugs
Innis Cunningham wrote:
Hi Curt
No this problem has been around since 9.5 or maybe before.At
least for the autothrottle.
What seems to be the problem is when the autothrottle is cycled
it changes the speed property in autopilot/locks from nothing to off.
And from then on you cant use page up/down t
Hi Curt
No this problem has been around since 9.5 or maybe before.At
least for the autothrottle.
What seems to be the problem is when the autothrottle is cycled
it changes the speed property in autopilot/locks from nothing to off.
And from then on you cant use page up/down to move the throttles.
I
For the last day to two I've been having some keyboard input problems.
Specifically, after activating (and then deactivating) the wing leveler,
I can no longer use the arrow keys to control the ailerons. After
activating (and then deactivating) the auto throttle, I can no longer
use the page
