20,741
edits
Howto:Troubleshooting Nasal Callbacks: Difference between revisions
Jump to navigation
Jump to search
Howto:Troubleshooting Nasal Callbacks (view source)
Revision as of 12:33, 1 February 2016
, 1 February 2016→Motivation
No edit summary |
|||
| Line 1: | Line 1: | ||
== Motivation == | == Motivation == | ||
{{FGCquote | |||
|1= it's relatively easy to do bad things unintentionally. Like tie a bit of code to an FDM property and run updates of a display 120 times per second rather than the 30 times you actually need. Like start a loop multiple times so that you update the same property 30 times per frame rather than the one time you actually need. It's actually pretty hard to catch these things, because the code is formally okay, does the right thing and just eats more performance than necessary, and there's no simple output telling you that you're running 30 loops rather than the one you expect. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34810857/ | |||
| title = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API</nowiki> | |||
| author = <nowiki>Thorsten Renk</nowiki> | |||
| date = Feb 1st, 2016 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
| Line 20: | Line 29: | ||
}} | }} | ||
}} | }} | ||
== Background == | == Background == | ||
{{FGCquote | {{FGCquote | ||