482
edits
Input device: Difference between revisions
Jump to navigation
Jump to search
→General tips: xml
(→General tips: xml) |
|||
| Line 283: | Line 283: | ||
* 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 | |||
& < -- | |||
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 "<". | |||
* 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. | * 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. | ||
| Line 294: | Line 301: | ||
* You can explore the internal property tree to see many variables that can be altered using joystick buttons or axes (File/Browse Internal Properties) | * You can explore the internal property tree to see many variables that can be altered using joystick buttons or axes (File/Browse Internal Properties) | ||
* All Nasal code shares a common namespace, so it's possible to set a variable in one nasal binding, and to read it in another. | |||
===Useful hints for scripts=== | ===Useful hints for scripts=== | ||