20,741
edits
Line 95: | Line 95: | ||
{{FGCquote|1= Note that as the QtLauncher transitions into a full GUI to replace the PUI GUI, many of these issues will disappear, and new ones will appear. In any case, debugging a modern GUI is much harder than debugging the non-GUI parts. A basic knowledge of threading, locks, and racing is quite useful for understanding and catching these bugs.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34431801/ | title = <nowiki>Re: [Flightgear-devel] Debug build / crash on exit</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = Sep 4th, 2015 }}}} | {{FGCquote|1= Note that as the QtLauncher transitions into a full GUI to replace the PUI GUI, many of these issues will disappear, and new ones will appear. In any case, debugging a modern GUI is much harder than debugging the non-GUI parts. A basic knowledge of threading, locks, and racing is quite useful for understanding and catching these bugs.|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34431801/ | title = <nowiki>Re: [Flightgear-devel] Debug build / crash on exit</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = Sep 4th, 2015 }}}} | ||
<references/> | |||
=== Canvas === | === Canvas === |