[Flightgear-devel] Joystick configurationc hange (Was: Upcoming v0.9.8 release)

2005-01-17 Thread Erik Hofman 
Oliver C. wrote:
In this case it depends on the following:
Does a definition get not defined when a value is missing?
Not anymore, I have committed a patch that ignores platforms that re not 
specified within the number/number section.

This is a heads  up for all joystick users:
 I have thought of possible problems with this, but the only one I 
could think of is when axis n= is defined for platforms that are not 
defined within the number/number section.

  !! This is bas behavior and should be corrected !!
For example, when this is the definition:
 axis
  descView Elevation (windows)/desc
  number
   windows7/windows
  /number

then what happens when FlightGear is started on a unix system?
It will be ignored in the latest code.
Does this definition get ignored or do we have an error because of
a NULL assignment?
axis
  descView Elevation (windows)/desc
  number
 -- NULL  for a UNIX OS? --   
  /number
This section will now be completely ignored (even if n= is specified 
in the axis tag).

Erik
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d

Re: [Flightgear-devel] Joystick configurationc hange (Was: Upcoming v0.9.8 release)

2005-01-17 Thread Oliver C. 
On Monday 17 January 2005 11:40, Erik Hofman wrote:
 Oliver C. wrote:
  In this case it depends on the following:
  Does a definition get not defined when a value is missing?

 Not anymore, I have committed a patch that ignores platforms that re not
 specified within the number/number section.

 This is a heads  up for all joystick users:
   I have thought of possible problems with this, but the only one I
 could think of is when axis n= is defined for platforms that are not
 defined within the number/number section.

!! This is bas behavior and should be corrected !!

Sounds okay for me.

But what about such a solution:

axis
   descView Elevation/desc
 number
unix5/unix
windows7/windows
 /number
 low
  repeatabletrue/repeatable
  binding
   commandproperty-adjust/command
   property/sim/current-view/goal-pitch-offset-deg/property
   windows 
   step type=double-1.0/step
   /windows
   unix
   step type=double1.0/step
   /unix
  /binding
 /low
 high
  repeatabletrue/repeatable
  binding
   commandproperty-adjust/command
   property/sim/current-view/goal-pitch-offset-deg/property
  windows
 step type=double1.0/step
  /windows
  unix
 step type=double-1.0/step
  /unix
  /binding
 /high
/axis

Could that be implemented?
IMO it is cleaner and more intuitive.
(intuitive because it was the first thing, that i tried by try and error
to make the axis inverted. :) )


Or what about this one?

   binding
   commandproperty-adjust/command
   property/sim/current-view/goal-pitch-offset-deg/property
step type=double
 windows-1.0windows
 unix1.0/unix
/step
/binding

Is it possible to implement such a behaviour?

Best Regards,
 Oliver C.



___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d