not only more consistent, but also makes the autopilot dialog act more like
the real device). Add a few rules. Move the checkboxes to the left, as it's
usually done in GUIs for switches that enable/disable a group of widgets.
leave edit field!, press <Return> to execute; as an example try
screen.log.write("hello world"), or f16.canopy.open() in the F16,
or bo105.doors[3].move(0.3) in the Bo105 etc.
I made a minor change to one file in the c172p that accommodates a
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the change
points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the change
points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
I made a minor change to one file in the c172p that accommodates a
feature I added to the navcom-kx155.xml and the dme.xml in the
Instruments folder. I wanted to leave the frequencies, etc. on these
dark until there was voltage applied to
/systems/electrical/outputs/nav. This was accomplished by adding a
param and property alias pointing to the appropriate value. Since the
c172p "always" applies 28 volts, this made no change in the c172p, but
allowed me to model the avionics master and battery master realisticly
in pa24-electrical.nas. I put in comments explaining this at the
change points.
There is a useful "help > aircraft help" that walks you through the
start procedure and lists the key bindings as well as the key to "light
up" the hot spots.
mode according to the switch position. Now dme.cxx is more generic
and can't make these settings any more -- and doesn't. So the dme
didn't display anything even if the knob was on.
The initialization has now to be done in the dme.xml file.
(Button-less actions are fired at init time and then thrown away.)
