FlightGear Newsletter October 2016: Difference between revisions

m
Update {{func link}} form
m (Protected "FlightGear Newsletter October 2016": Publishing newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite)))
m (Update {{func link}} form)
 
Line 80: Line 80:
}}</ref> However, performance tests indicate that the cause of the bottleneck is the huge amount of [[Property Tree|property]] manipulation involved during each update, ''after'' the actual calculations have been completed. This has also been shown to be a problem for any very complex Canvas.
}}</ref> However, performance tests indicate that the cause of the bottleneck is the huge amount of [[Property Tree|property]] manipulation involved during each update, ''after'' the actual calculations have been completed. This has also been shown to be a problem for any very complex Canvas.


Some ways to help reduce bottlenecks include using {{func link|getprop}}/{{func link|setprop}} instead of [[Nasal library/props|props.nas APIs]] and using variables instead of properties where possible.<ref>{{cite web
Some ways to help reduce bottlenecks include using {{func link|getprop()}}/{{func link|setprop()}} instead of [[Nasal library/props|props.nas APIs]] and using variables instead of properties where possible.<ref>{{cite web
|url    = https://sourceforge.net/p/flightgear/mailman/message/30724363/  
|url    = https://sourceforge.net/p/flightgear/mailman/message/30724363/  
|title  = <nowiki>Re: [Flightgear-devel] Nasal props API relative path support</nowiki>
|title  = <nowiki>Re: [Flightgear-devel] Nasal props API relative path support</nowiki>