Paul Surgeon wrote: > On Thursday, 4 December 2003 22:35, Frederic Bouvier wrote: > > I just want to point out here that axis are not the same for Linux and > > Windows : axis 2 & 3 are inverted, and the hat axis are not the same > > ( 4&5 for Linux, 6&7 for Windows ). > > I just checked and you are correct - the axis are swapped between Doze and > Linux. :-| > > > From the header of your message, > > I presume you are running Linux, so if your patch is commited, the guy > > that submit the previous one because his Windows setup didn't work > > will resubmit another to "correct" the behaviour broken for him > > I think this is what has happened because I very clearly remember having the > same problem with the Windows port a while back. (Well over a year ago) > > > There is a risk of an endless loop here as you already detected it is > > an ongoing problem. > > How does one check the CVS history of a file? > I've used WinCVS before but I'm a bit new on the command line version. > I want to see who has modified that xml binding file over the last couple of > years.
http://cvs.flightgear.org/cgi-bin/viewcvs/viewcvs.cgi/?cvsroot=FlightGear-0.9 > > For other joysticks, the description name differs but it seems that > > this one share the same name on both systems. > > Yes, the name is the same on both systems. That's unfortunate. > > So a correct, definitive, patch would be to discriminate bindings and > > only load those for the system where FG runs. > > Yes that makes sense. > How about having two binding files for the stick like : > sidewinder-force-feed-pro-unix.xml > sidewinder-force-feed-pro-windows.xml > Then when FG loads and detects a sidewinder-force-feed-pro stick it can just > load the correct bindings for the platform. > > The best place to do this is probably at compile time with a #ifdef WIN32 type > of statement that declares which sidewinder binding to use. > There is no need to do it dynamically at runtime. Actually, all bindings are included in $FG_ROOT/joysticks.xml, so it is this file that needs to be forked. Not a bad idea after all ;-) -Fred _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
