Input device: Difference between revisions

Jump to navigation Jump to search
m
no edit summary
m (Updated to mention the ability to reload settings without restarting the program)
mNo edit summary
Line 315: Line 315:
* Errors can be detected on initial startup or at runtime. Both types of errors will be displayed in the terminal.
* Errors can be detected on initial startup or at runtime. Both types of errors will be displayed in the terminal.
* One of the most common errors is including a character that makes XML choke. Such characters include<br>& < --<br>These characters will cause problems even if simply included in comments or within scripts.
* One of the most common errors is including a character that makes XML choke. Such characters include<br>& < --<br>These characters will cause problems even if simply included in comments or within scripts.
* If your scripts contain any of these characters, you have to enclose the scripts in <script><![CDATA[...]]></script>. Alternatively, you can 'escape' the characters, ie "<" becomes "&lt;".
* If your scripts contain any of these characters, you have to enclose the scripts in <script><![CDATA[...]]></script>. Alternatively, you can 'escape' the characters, ie "<" becomes "&amp;lt;".
* You can reload your edited joystick file without restarting FlightGear by selecting "Debug" &gt; "Reload Input" from the main simulator window.
* You can reload your edited joystick file without restarting FlightGear by selecting "Debug" &gt; "Reload Input" from the main simulator window.
* You can find many examples of different ways to program joysticks simply by examining the joystick xml files that are packaged with FlightGear. See the directory FlightGear/data/input/joysticks
* You can find many examples of different ways to program joysticks simply by examining the joystick xml files that are packaged with FlightGear. See the directory FlightGear/data/input/joysticks
395

edits

Navigation menu