Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-20 Thread Brandon Bergren
$USERPROFILE on WinNT shold resolve to the root of the users home directory. $SYSTEMROOT should resolve to the operating system root directory. If I remember right, there is a portable way to find the my documents folder. (ie, win9xnt, any language.) I know the BZFlag project is able to find

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-05 Thread David Megginson
The Tone'ster writes: IMHO, it would be nice to see default config file names and locations be names that would work across all platforms and to see that they land in places on a given OS that have analogies to each other. Better, IMHO, would be to keep default configuration info

re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread David Megginson
Paul Deppe writes: It looks like it is not possible to specify an --aircraft in system.fgfsrc because the aircraft model is loaded before system.fgfsrc is processed (see program output below). Is this the intended behavior? I thought the processing order was supposed to be 1)

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread Michael Basler
David, From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David Megginson We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line I

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread David Megginson
Michael Basler writes: We were planning to drop system.fgfsrc -- I thought we already had, but I guess it's still lurking. The processing order, from memory, is $FG_ROOT/preferences.xml $HOME/.fgfsrc command line I don't fully understand this. Until now,

Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread Norman Vine
David Megginson writes: Paul Deppe writes: It looks like it is not possible to specify an --aircraft in system.fgfsrc because the aircraft model is loaded before system.fgfsrc is processed (see program output below). Is this the intended behavior? I thought the processing order

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread Michael Basler
David, The idea was that system.fgfsrc is system-wide, while .fgfsrc is per-user. For Windows, perhaps we should look for fgfs.cfg in My Documents or wherever (is there any concept of separate user directories yet?). Win XP and 2000 allow management of separate user directories under the

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread David Megginson
Michael Basler writes: Personally I've got most of my user's files just on a separate partition (and all the FlightGear stuff on yet another partition and FS2002 on yet another one and so on). From my POV the mechanism we had with just a single system.fgfsrc in $FG_ROOT would be

RE: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread The Tone'ster
--- David Megginson [EMAIL PROTECTED] wrote: The idea was that system.fgfsrc is system-wide, while .fgfsrc is per-user. For Windows, perhaps we should look for fgfs.cfg in My Documents or wherever (is there any concept of separate user directories yet?). $USERPROFILE on WinNT shold resolve

Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread Geoff McLane
Dear All, oops, pardon moi ... RE:MSVC6 Update - continued ... This i added, explicily, to fg_init.cxx // Next check the 'root' for a system.fgfsrc file if ( aircraft.empty() ) { // Check for $fg_root/system.fgfsrc SGPath config( globals-get_fg_root() );

Re: [Flightgear-devel] Cannot specify --aircraft in system.fgfsrc

2002-12-04 Thread Curtis L. Olson
Geoff McLane writes: PS: Curt, did you not get my README.msvc6? Or you do not feel it should be in the CVS just yet? Hmmm, I don't recall, you probably want to send it again. If I did get it, it is now very buried in my email pile. Curt. -- Curtis Olson IVLab / HumanFIRST Program