This thread brings up a good question:  How do you override the default
config files (or any file in FGBASE) without creating an entire copy of
the FGBASE directory (besides symlinks...think cross-platform)?  IMHO, I
think we should consider using a personal ~/.fgfs/ directory for each
user that contains files they wish to overrite or suppliment.

For example, say I'm a long-time X-Plane user and just can't live with
the default FG key bindings.  I could create my very own
~/.fgfs/keyboard.xml and completely override the master file.

Another example:  say I like the default key bindings but want to add a
few custom bindings.  I could create a ~/.fgfs/keyboard.xml and
<include> the master (effectingly loading the defaults) and then add my
custom keys below that.

The possibilities are really endless, I think.  We could go so far as to
allow a user to override any file in the FGBASE dir and even adding new
files not in the FGBASE dir.

The basic logic is simple, but I'm not sure how much code would need to
redone to get this to work.

Thanks

* [EMAIL PROTECTED] (Alex Perry) [2002.04.27 21:55]:
> You should have a look at the bindings in your joystick.xml file
> as there a bunch of defaults in there that you probably won't like.
> 
> I locally have a chproducts.xml file which is used inside the preferences.xml
> file instead of the standard joystick.xml file, so that CVS doesn't keep
> whingeing about all my little local variations.
> 
> > Hello again,
> > 
> >     To set the stage, running the current CVS version of everything, on a 
> > P2-300 Linux machine with kernel 2.4.18. Interfacing with CH Flight Sim 
> > Yoke USB and CH Pro Pedals USB. Working great with the default c172, now 
> > that the old (failed) Nvidia card is replaced with a GeForce2MX.
> > 
> >     Just tried the c310, triggered by comments on its progress, and I fully 
> > agree. Did some tweaking to my .fgfsrc to handle the dual engines, and 
> > everything looked good at first. An extract of said file is below (cut a 
> > bit to save space). Further trials showed an interaction between the 
> > rudder pedals and the right throttle.
> > 
> >     Initially, throttle worked as expected, ganged because of a shortage of 
> > input axes. A slight touch on either pedal makes the right throttle jump 
> > to half scale, and then the throttle tracks the pedal movement. With 
> > pedals still, any change of the hand throttle recaptures control.
> > 
> >     This is what I would expect if event records from the rudder pedals were 
> > leaking into the throttle "circuit". I checked for other interactions, 
> > such as the reverse direction, but
> > this is the only one I could spot. The question is where and why.
> > 
> >     Running js_demo shows all axes working, and no interaction in this 
> > program. Is there a small bug in the command parsing or (more likely) an 
> > error in my configuration caused by my limited understanding?
> > 
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/property=/controls/throttle[0]
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/command=property-scale
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/squared=false
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/dead-band=0.00
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/factor=-0.5
> > --prop:/input/joysticks/js[1]/axis[2]/binding[0]/offset=-1.0
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/property=/controls/throttle[1]
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/command=property-scale
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/squared=false
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/dead-band=0.00
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/factor=-0.5
> > --prop:/input/joysticks/js[1]/axis[2]/binding[1]/offset=-1.0
> > #
> > --prop:/input/joysticks/js[0]/axis[2]/binding/property=/controls/rudder
> > --prop:/input/joysticks/js[0]/axis[2]/binding/command=property-scale
> > --prop:/input/joysticks/js[0]/axis[2]/binding/squared=false
> > --prop:/input/joysticks/js[0]/axis[2]/dead-band=0.00
> > --prop:/input/joysticks/js[0]/axis[2]/binding/offset=0.0
> > --prop:/input/joysticks/js[0]/axis[2]/binding/factor=1.0
> > #

-- 
Cameron Moore
[ I have an inferiority complex.  But it's not a very good one. ]

_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to