On Sunday 16 January 2005 21:07, Erik Hofman wrote:
> Oliver C. wrote:
> >>Would this work just by defining two sections for the specific bindings,
> >>like this:
> >>
> >>
> >> <axis>
> >> <desc>View Elevation (Default)</desc>
> >> <number>
> >> <unix>5</unix>
> >> </number>
> >>
> >> <axis>
> >> <desc>View Elevation (windows)</desc>
> >> <number>
> >> <windows>7</windows>
> >> </number>
> >
> > The problem is, how do you define which section should be used by which
> > OS?
>
> If you look at the code above you see that one has only an axis number
> for unix and the other has only an axis number defined for windows. I
> was wondering if this is accepted by the current code already.
>
> Erik
>
Now i understand what you meant.
In this case it depends on the following:
Does a definition get not defined when a value is missing?
For example, when this is the definition:
> >> <axis>
> >> <desc>View Elevation (windows)</desc>
> >> <number>
> >> <windows>7</windows>
> >> </number>
then what happens when FlightGear is started on a unix system?
Does this definition get ignored or do we have an error because of
a NULL assignment?
<axis>
<desc>View Elevation (windows)</desc>
<number>
<-- NULL for a UNIX OS? -->
</number>
....
Does anyone know more about that?
Best Regards,
Oliver C.
_______________________________________________
Flightgear-devel mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
