482
edits
Input device: Difference between revisions
Jump to navigation
Jump to search
m
→General tips
m (→General tips) |
|||
| Line 280: | Line 280: | ||
==More about programming joystick XML files== | ==More about programming joystick XML files== | ||
===General tips=== | ===General tips=== | ||
* When testing a new xml file it is best to start | * When testing a new xml file it is best to start FlightGear via a command window (rather than the GUI interface). Any error messages will then be displayed in the terminal. Error messages will give both a message and a line number, helping you pinpoint any errors. | ||
* 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. | ||
* Note that as of ver 1.9.1 there appears to be no way to tell FlightGear to reload joystick files at runtime. So to test any changes to your file you must | * Note that as of ver 1.9.1 there appears to be no way to tell FlightGear to reload joystick files at runtime. So to test any changes to your file you must exit FlightGear and re-start, a somewhat time-consuming process. | ||
* You can find many examples of different ways to program joysticks simply by examining the joystick xml files that are packaged with FlightGear. | * You can find many examples of different ways to program joysticks simply by examining the joystick xml files that are packaged with FlightGear. | ||