David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently. Previously you could type Shift-1
Shift-2 Shift-3 ... etc. to select an engine. Then '{' and '}'
would select the magnetos. Finally, space bar would kick in the
starter motor for as
Curtis L. Olson wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently.
This one is mine. The recent Nasal stuff contains a rework of the
engine handling to allow for arbitrary numbers of engines, and avoid
the why are there 10
On Mon, 29 Dec 2003 15:49:30 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently. Previously you could type Shift-1
Shift-2 Shift-3 ... etc. to select an engine. Then '{' and '}'
would
Andy Ross writes:
Curtis L. Olson wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently.
This one is mine. The recent Nasal stuff contains a rework of the
engine handling to allow for arbitrary numbers of engines, and
Jon S Berndt writes:
On Mon, 29 Dec 2003 15:49:30 -0600
Curtis L. Olson [EMAIL PROTECTED] wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently. Previously you could type Shift-1
Shift-2 Shift-3 ... etc. to select an
Andy Ross writes:
Curtis L. Olson wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently.
This one is mine. The recent Nasal stuff contains a rework of the
engine handling to allow for arbitrary numbers of engines, and
Andy Ross writes:
Curtis L. Olson wrote:
David, (Andy?)
It appears that in the latest cvs, we have lost the ability to control
the engines independently.
This one is mine. The recent Nasal stuff contains a rework of the
engine handling to allow for arbitrary numbers of engines, and
Curt wrote:
select = sel.getChild(engine, i);
Could there be a bug in this form of getChild()?
Heh, bingo. That was exactly it. See the other post for notes.
Andy
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Curtis L. Olson wrote:
It appears (to me) to be a property setting problem. Andy, does
nasal have the ability to dump console output for temporary
debugging?
Sure, there's a print() function which uses SG_LOG; for exactly this
purpose. There's even a fancy dump() method on a property node
Andy Ross writes:
Sure, there's a print() function which uses SG_LOG; for exactly this
purpose. There's even a fancy dump() method on a property node that
you can use to dump a property tree to the console.
Ok, thanks, I eventually found it. Quite useful, thanks. :-)
It turns out to be a
10 matches
Mail list logo
