Erik Hofman said:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Input
In directory baron:/tmp/cvs-serv26245
Modified Files:
input.cxx input.hxx
Log Message:
Make it possible to define a target-platform tag in the joystick
configuration file. This would make it possible to have
* Jim Wilson -- Tuesday 27 April 2004 15:12:
Erik Hofman said:
Make it possible to define a target-platform tag in the joystick
configuration file. This would make it possible to have different
configuration files for Windows.
Just curious, why is this required?
Because Unix and Windows
Melchior FRANZ wrote:
* Jim Wilson -- Tuesday 27 April 2004 15:12:
Erik Hofman said:
Make it possible to define a tag in the joystick
configuration file. This would make it possible to have different
configuration files for Windows.
Just curious, why is this required?
Because
Jim Wilson wrote:
Erik Hofman checked in:
Make it possible to define a target-platform tag in the joystick
configuration file. This would make it possible to have different
configuration files for Windows. Possible values are: Windows, UNIX
or All. Not specifying the tag equals to 'All'.
* Frederic Bouvier -- Tuesday 27 April 2004 15:49:
Melchior FRANZ wrote:
Because Unix and Windows don't always agree on axis numeration.
In fact, they never agree. axis 2 3 are reverted, and the hat has
different numbering, for the same joystick name.
So we'd need two config files for
On Tue, 27 Apr 2004 06:58:41 -0700
Andy Ross [EMAIL PROTECTED] wrote:
Many/most of the joysticks don't work for windows users. They
download the program, try it, and then complain when the view is
constantly spinning around. One presumes the axis mappings are
simply different between the
Melchior FRANZ wrote:
So we'd need two config files for *every* joystick (with more than
two axes)? That's IMHO not acceptable. I'd rather prefer a mechanism
that makes one and the same config file work for both systems then.
After endless times of no discussion and no solutions I hacked
Erik Hofman wrote:
After endless times of no discussion and no solutions I hacked
something together that works for every situation. Not acceptable
won't do in this case unless I see something show up that is elegant
and that works in every situation.
Agreed. We need to get something
axes as defined in the file.
Richard
-Original Message-
From: Erik Hofman [mailto:[EMAIL PROTECTED]
Sent: 27 April 2004 3:21 pm
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs]CVS:
FlightGear/src/Input input.cxx, 1.43, 1.44 input.hxx, 1.17
* Erik Hofman -- Tuesday 27 April 2004 16:21:
Melchior FRANZ wrote:
So we'd need two config files for *every* joystick (with more than
two axes)? That's IMHO not acceptable.
Not acceptable won't do in this case unless I see something show up
that is elegant and that works in every
On Dienstag, 27. April 2004 16:33, Melchior FRANZ wrote:
* Erik Hofman -- Tuesday 27 April 2004 16:21:
Melchior FRANZ wrote:
So we'd need two config files for *every* joystick (with more than
two axes)? That's IMHO not acceptable.
Not acceptable won't do in this case unless I see
Melchior FRANZ wrote:
* Erik Hofman -- Tuesday 27 April 2004 16:21:
Melchior FRANZ wrote:
So we'd need two config files for *every* joystick (with more than
two axes)? That's IMHO not acceptable.
Not acceptable won't do in this case unless I see something show up
that is elegant and that works
* Erik Hofman -- Tuesday 27 April 2004 16:37:
I bet you can come up with a clever solution where only the platform
specific part are in the actual configuration file and everything else
gets included from a shared file ...
axis unix=2 windows=3
descRudder/desc
binding
* Melchior FRANZ -- Tuesday 27 April 2004 16:49:
* Erik Hofman -- Tuesday 27 April 2004 16:37:
I bet you can come up with a clever solution where only the platform
specific part are in the actual configuration file and everything else
gets included from a shared file ...
axis
Melchior FRANZ wrote:
Whereby unix would be an alias for n and the line could also be
written as
axis n=2 windows=3
This is syntactically cleaner, but the code changes required are
severe. XML Attributes in property files are interpreted only by the
SimGear property parser, they aren't
* Andy Ross -- Tuesday 27 April 2004 17:23:
Melchior FRANZ wrote:
axis n=2 windows=3
This is syntactically cleaner, but the code changes required are
severe. XML Attributes in property files are interpreted only by the
SimGear property parser, they aren't available in the resulting
Melchior FRANZ wrote:
* Andy Ross -- Tuesday 27 April 2004 17:23:
Melchior FRANZ wrote:
axis n=2 windows=3
This is syntactically cleaner, but the code changes required are
severe. XML Attributes in property files are interpreted only by the
SimGear property parser, they aren't available in
* Erik Hofman -- Tuesday 27 April 2004 17:50:
Right now code other than SimGear's property I/O code can access the
attributes. To get this working I need to access them in FlightGear, but
every(?) attribute other than n= is disregarded...
I still don't get it. In props_io.cxx:164ff, why
* Melchior FRANZ -- Tuesday 27 April 2004 18:20:
winval = atts.getValue(n_win);// or windows
[...]
if (winval != -1 current_os == windows)
[...]
... assuming that a non existent attribute returns -1.
It's a string or char* and does of course return 0. :-)
m.
to virtual
axes as defined in the file.
Richard
-Original Message-
From: Erik Hofman [mailto:[EMAIL PROTECTED]
Sent: 27 April 2004 3:21 pm
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Re: [Flightgear-cvslogs]CVS:
FlightGear/src/Input input.cxx, 1.43
20 matches
Mail list logo