David Culp wrote:
Where would be the appropriate place to
look for such a file at runtime -- where should this file live?
It looks to me like FlightGear could use a Config directory. It would
hold
preferences.xml, joystick.xml, keyboard.xml, materials.xml, mice.xml,
menu.xml,
Jon Berndt wrote:
For JSBSim standalone I think we would have a file that sits in the base
directory (from which JSBSim is run) or specified in an environment variable
JSBSIM_ROOT. This file I am referring to for JSBSim would serve to set up
simulation specific (something that is not or should
If it doesn't need to be in a user friendly way you could specify
something like this in your ~/.fgfsrc file:
--prop:/jsbsim/config/integrator=mytype
--prop:/jsbsim/config/logging=true
--prop:/jsbsim/config/atmosphere=mars
That would require _no_ action from the FlightGear side.
Erik
I may want to create a configuration file for JSBSim that controls
simulation specific items that will likely not change often. These may
include items such as the particular type of numeric integrator to use for
various of our integrations. It would also include output logging
information
Where would be the appropriate place to
look for such a file at runtime -- where should this file live?
It looks to me like FlightGear could use a Config directory. It would hold
preferences.xml, joystick.xml, keyboard.xml, materials.xml, mice.xml,
menu.xml, options.xml as well as a
