20,741
edits
Howto:Troubleshooting Nasal Callbacks: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Troubleshooting Nasal Callbacks (view source)
Revision as of 20:45, 31 January 2016
, 31 January 2016→Background: +ref
m (→Background: +ref) |
|||
| Line 1: | Line 1: | ||
== Background == | == Background == | ||
{{FGCquote | |||
|1= Without the patch, thousands of listeners were triggered each frame | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/32774953/ | |||
| title = <nowiki>Re: [Flightgear-devel] crash in SGPropertyNode::fireValueChanged</nowiki> | |||
| author = <nowiki>Torsten Dreyer</nowiki> | |||
| date = Aug 29th, 2014 | |||
| added = Aug 29th, 2014 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote | ||
|1= Someone recently pointed out that the setlistener() / removelistener() API makes it easy to leak resources. So I wondered about making an alternate API where the return value from setlistener '''must''' be kept, or the listener is removed. I can imagine this with a helper object | |1= Someone recently pointed out that the setlistener() / removelistener() API makes it easy to leak resources. So I wondered about making an alternate API where the return value from setlistener '''must''' be kept, or the listener is removed. I can imagine this with a helper object | ||