20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
→Repercussions
(→Canvas) |
m (→Repercussions) |
||
| Line 67: | Line 67: | ||
If, how and when the internal gui can leverage Qt is under investigation and in such an early state that those responsible preferred to not announce anything yet. If this ever happens, this will be discussed on the mailing list<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref> | If, how and when the internal gui can leverage Qt is under investigation and in such an early state that those responsible preferred to not announce anything yet. If this ever happens, this will be discussed on the mailing list<ref>http://forum.flightgear.org/viewtopic.php?p=229563#p229563</ref> | ||
=== Race Conditions === | |||
{{FGCquote|1= Should installing an aircraft to the proper aircraft folder be allowed to crash the launcher if that plane has an error the launcher can detect or should maybe the launcher load and report an error somewhere visible in the launchers gui?|2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34430800/ | title = <nowiki>Re: [Flightgear-devel] fgaddon c310 typos??</nowiki> | author = <nowiki>Ray St. Marie</nowiki> | date = Sep 3rd, 2015 }}}} | |||
{{FGCquote|1= The problem with GUI coding is that it is very, very hard - it is much more problematic than normal coding and causes far more headaches (from all the banging of your head against the wall trying to work out why it is racing and segfaulting on one system and not another). |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34430850/ | title = <nowiki>Re: [Flightgear-devel] fgaddon c310 typos??</nowiki> | author = <nowiki>Edward d'Auvergne</nowiki> | date = Sep 3rd, 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 }}}} | |||
=== Canvas === | === Canvas === | ||