20,741
edits
FlightGear Qt launcher: Difference between revisions
Jump to navigation
Jump to search
m
→Announcement
m (→Announcement) |
|||
| Line 28: | Line 28: | ||
All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | All of this would be a QtQuick 2 GUI, not a Qt widgets GUI. If you don’t know what that terminology means, don’t worry about it, the quick answer is it works the same ways as Canvas does at present (rendering to OpenGL). | ||
{{FGCquote | |||
|1= the intention is we’re adding integrated convenience features but the command line / shell environment won’t change and the default mode of ‘fgfs’ even in a Qt-enabled build is unchanged. You need set an env var or pass an argument to get the launcher, even if the feature was selected at compile time. We have the advantage that the Windows and Mac pre-built builds, it’s easy to ensure Qt is available, and those users are less likely to want complex command-line control than Linux users. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34532040/ | |||
| title = <nowiki>[Flightgear-devel] GUI questions (again)</nowiki> | |||
| author = <nowiki>James Turner</nowiki> | |||
| date = Oct 11th, 2015 | |||
| added = Oct 11th, 2015 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
== Status == | == Status == | ||