20,741
edits
Canvas Threading: Difference between revisions
Jump to navigation
Jump to search
→Problem
m (→Background: https://forum.flightgear.org/viewtopic.php?f=30&t=36614&p=357608&hilit=#p357243) |
|||
| Line 62: | Line 62: | ||
For the time being, the free-form nature of Canvas/Nasal based avionics means that most avionics don't use any dedicated frameworks or standard patterns to formalize if/how and when crucial state is updated. | For the time being, the free-form nature of Canvas/Nasal based avionics means that most avionics don't use any dedicated frameworks or standard patterns to formalize if/how and when crucial state is updated. | ||
This includes property tree state, as well as other state | This includes property tree state, as well as other state retrieved via FlightGear extension functions (think Nasal/cppbind). | ||
Thus, a number of complex cockpits have been demonstrated to be affected by the number of Nasal/Canvas based displays. Often, this is due to the structure of existing legacy code. | Thus, a number of complex cockpits have been demonstrated to be affected by the number of Nasal/Canvas based displays. Often, this is due to the structure of existing legacy code. | ||