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(
"/sim/dimensions/radius-m",
"/sim/dimensions/parkpos-offset-m",
"/sim/aircraft-class",
" /sim/aircraft-operator"
);
]]></script>
</MyModule>
</nasal>
To add this globally for all aircraft, probably
$FGDATA/Nasal/aircraft.nas would be a good place for this code.
Torsten
Am 21.09.2011 09:03, schrieb Durk Talsma:
> 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 called
> "acopsdata.nas" containing:
>
> aircraft.data.add(
> "/sim/dimensions/radius-m",
> "/sim/dimensions/parkpos-offset-m",
> "/sim/aircraft-class",
> " /sim/aircraft-operator"
> );
>
> and copy that to the SenecaII nasal directory, would that interfere with your
> existing nasal code?
>
> Cheers,
> Durk
>
> On 20 Sep 2011, at 23:07, Torsten Dreyer wrote:
>
>> 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.
>>
>> aircraft.data.add(
>> "/one/property",
>> "/another/property",
>> "/and/another/property"
>> );
>>
>> Torsten
>>
>> ------------------------------------------------------------------------------
>> All the data continuously generated in your IT infrastructure contains a
>> definitive record of customers, application performance, security
>> threats, fraudulent activity and more. Splunk takes this data and makes
>> sense of it. Business sense. IT sense. Common sense.
>> http://p.sf.net/sfu/splunk-d2dcopy1
>> _______________________________________________
>> Flightgear-devel mailing list
>> Flightgear-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
