* David Megginson -- Thursday 21 February 2002 15:26:
[...]
> This is a little ugly, but ordinary users should never have to see
> it. Now, the user can put
>
> -prop:/config/aircraft/dc3-dpm/sim/model/path=Models/dc3-usa.ac
>
> in her .fgfsrc and get a different 3D model for the DC-3 without
> screwing up the default configurations for any other aircraft.
Wouldn't it be simpler (and more elegant), if fgfs would always look
for a local config file that would take precedence over the system
config as follows:
fgfs --aircraft=dc3-yasim-set.xml
Now fgfs would =first= look if there's a file ~/.fgfs/dc3-yasim-set.xml
and load this file, completely ignoring the system wide file with the
same name. The local file could now define pretty much the same as the
system config with a few modifications, or (preferably) explicitly load
the system wide config first and just add the modifications:
<!-- ~/.fgfs/dc-yasim-set.xml>
<!-- load the system config ... -->
<Include $FGROOT/Aircraft/dc-yasim-set.xml>
<!--- ... but change the model -->
<PropertyList>
<model>
<path>Aircraft/dc3/Models/dc3-dpm.ac</path>
</model>
<PropertyList>
This would IMHO be a lot cleaner.
m.
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
