* Durk Talsma -- Wednesday 21 September 2011:
1). Is there a 1 to 1 correspondence between the value of the /sim/aircraft
property and the name of the xml file where aircraft specific properties will
be saved in?
Yes. The path is generated in aircraft.data.init
Hi Torsten,
I looked at your seneca file, briefly, but didn't really find a way to
translate this to the 777 sittuation. Being a complete nasal newbie, can I just
add this function to any existing nasal script, or could I even put this code
into a new file? Say I'm creating a new nasal file
hi Emilian,
On 20 Sep 2011, at 22:56, Emilian Huminiuc wrote:
Adding archive=y to the property tag?:
new-archived-property archive=ymyprop/new-archived-property
That's how I thought it should work, but I don't get this to work. After some
more experimentation, I found that I can save the
No it wouldn't interfere because it wouldn't get executed unless you
explicitly add it to the *-set.xml's nasal section. Either as a link
to a *.nas file or coded inline like this:
nasal
SomeOtherModule
...
/SomeOtherModule
MyModule
script![CDATA[
aircraft.data.add(
* Torsten Dreyer -- Wednesday 21 September 2011:
nasal
MyModule
script![CDATA[
aircraft.data.add(
/sim/dimensions/radius-m,
/sim/dimensions/parkpos-offset-m,
[...]
Or just:
sim
aircraft-data
path/sim/dimensions/radius-m/path
Or just:
sim
aircraft-data
path/sim/dimensions/radius-m/path
path/sim/dimensions/parkpos-offset-m/path
path/sim/aircraft-class/path
/aircraft-data
/sim
from where it's read by aircraft.nas already.
Excellent! I'm learning something
* Melchior FRANZ -- Wednesday 21 September 2011:
sim
aircraft-data
path/sim/dimensions/radius-m/path
I admit that this looks silly: why create properties that contain property
paths,
and not mark those properties with a flag right away, like with archive and
userarchive?
Hi Mechior, Torsten
On 21 Sep 2011, at 12:57, Melchior FRANZ wrote:
* Melchior FRANZ -- Wednesday 21 September 2011:
sim
aircraft-data
path/sim/dimensions/radius-m/path
I admit that this looks silly: why create properties that contain property
paths,
and not mark those
* Durk Talsma -- Wednesday 21 September 2011:
Just a quick question: Is this documented somewhere?
Don't think so. Only in the code, that is.
If not, I might start a short wiki page documenting the logic behind
archieve, userarchieve, and the interactions with the nasal system.
userarchive
* Melchior FRANZ -- Wednesday 21 September 2011:
userarchive simply marks what gets written to $FG_HOME/preferences.xml
Whoops ... to $FG_HOME/autosave.xml. (preferences.xml was used first, but
a bad idea and changed later.)
m.
On 21 Sep 2011, at 11:12, Melchior FRANZ wrote:
sim
aircraft-data
path/sim/dimensions/radius-m/path
path/sim/dimensions/parkpos-offset-m/path
path/sim/aircraft-class/path
/aircraft-data
/sim
Alright succes!!! Adding this section did the trick of
Hi all,
In referral to my previous posting: Can anybody tell me (or point me to
documentation) how I can specify new property in an aircraft -set.xml file, and
ensure that any changes to this property are saved in an aircraft specific data
file. As an example in the 777-200ER-set.xml, I have
On Tuesday 20 September 2011 23:25:51 Durk Talsma wrote:
Hi all,
In referral to my previous posting: Can anybody tell me (or point me to
documentation) how I can specify new property in an aircraft -set.xml
file, and ensure that any changes to this property are saved in an
aircraft specific
Am 20.09.2011 22:25, schrieb Durk Talsma:
how I can specify new property in an aircraft -set.xml file, and ensure that
any changes to this property are saved in an aircraft specific data file.
Just add this to you aircraft's nasal code so it gets executed once
during startup.
14 matches
Mail list logo
