better explanation
This commit is contained in:
parent
f74b2f5c23
commit
cec6d6cf5b
1 changed files with 10 additions and 8 deletions
|
@ -1,21 +1,23 @@
|
|||
<?xml version="1.0"?>
|
||||
<!--
|
||||
To override "named" joystick drivers add <js-named> entries
|
||||
with paths relative to the directory where the joysticks.xml
|
||||
file resides (first example). Such "named" drivers are only
|
||||
picked up if their <name> tags match the joystick hardware.
|
||||
They have precedence over already existing drivers with the
|
||||
same <name>. (You can also add a <name>default</name> entry
|
||||
to the driver to make it the default choice.)
|
||||
To override or add "named" joystick drivers list them in
|
||||
<js-named> entries with paths relative to the directory where
|
||||
the joysticks.xml file resides (first example). Such "named"
|
||||
drivers are only picked up if one of their <name>s matches
|
||||
the joystick hardware (see output of the js_demo application).
|
||||
These drivers have precedence over already existing drivers
|
||||
with the same <name>. (You can also add a <name>default</name>
|
||||
entry to the driver to make it the default choice.)
|
||||
|
||||
The second example shows how to load a driver directly to
|
||||
position 0. It will then be used for the first joystick on
|
||||
position 0. This will then be used for the first joystick on
|
||||
your system and FlightGear will not overwrite it.
|
||||
-->
|
||||
|
||||
<PropertyList>
|
||||
<!--
|
||||
<js-named include="Input/Joysticks/Local/X45-modified.xml"/>
|
||||
|
||||
<js n="0" include="Input/Joysticks/Local/joystick_0.xml"/>
|
||||
-->
|
||||
|
||||
|
|
Loading…
Reference in a new issue