* SydSandy -- Monday 28 January 2008:
Does anyone have any objection to binding the mixture M/m
control to the Condition control , since they both are fuel
controls on different engines ?
I object.
The functions controls.mixtureAxis() and controls.adjMixture()
should only do what their
On Mon, 28 Jan 2008 09:39:46 +0100
Melchior FRANZ [EMAIL PROTECTED] wrote:
* SydSandy -- Monday 28 January 2008:
Does anyone have any objection to binding the mixture M/m
control to the Condition control , since they both are fuel
controls on different engines ?
I object.
The
As a third possibility, you could define a simple alias in the
*-set.xml file:
controls
engines
engine n=0
condition alias=/controls/engines/engine[0]/mixture/
/engine
/engines
/controls
Then you can use the condition property as much as you
On Mon, 28 Jan 2008, Melchior FRANZ wrote:
* SydSandy -- Monday 28 January 2008:
Does anyone have any objection to binding the mixture M/m
control to the Condition control , since they both are fuel
controls on different engines ?
I object.
The functions controls.mixtureAxis() and
On Sun, 27 Jan 2008 18:37:19 -0800
SydSandy [EMAIL PROTECTED] wrote:
Does anyone have any objection to binding the mixture M/m control to the
Condition control , since they both are fuel controls on different engines ?
Here I have just set this in the controls.nas file ...
var mixtureAxis
Does anyone have any objection to binding the mixture M/m control to the
Condition control , since they both are fuel controls on different engines ?
Here I have just set this in the controls.nas file ...
var mixtureAxis = func {
var val = cmdarg().getNode(setting).getValue();
6 matches
Mail list logo