FlightGear Qt launcher: Difference between revisions

Jump to navigation Jump to search

FlightGear Qt launcher (view source)

Revision as of 10:19, 14 March 2015

107 bytes removed ,  14 March 2015
m
no edit summary
No edit summary
mNo edit summary
Line 28: Line 28:
The launcher is not run by default, this is because it was created as a Mac only solution. We need to have the discussion if it should become the default launcher for Windows (Linux and other Unixes are less relevant, it’s up to the distribution packagers).
The launcher is not run by default, this is because it was created as a Mac only solution. We need to have the discussion if it should become the default launcher for Windows (Linux and other Unixes are less relevant, it’s up to the distribution packagers).


You can test the launcher by passing the <code>--launcher</code> argument, or setting the FG_LAUNCHER env var. These options exist to allow a Windows shortcut, .desktop file on Linux or the app bundle’s Info.plist to set the value when started from the GUI.
You can test the launcher by passing the <code>--launcher</code> argument, or setting the <code>$FG_LAUNCHER</code> environment variable. These options exist to allow a Windows shortcut, .desktop file on Linux or the app bundle’s Info.plist to set the value when started from the GUI.


And if you run fgfs via the command line with some options, you don’t get troubled by the launcher - the idea being to minimise how much of my life I spend being shouted at by the Internet. Which is already way more than I would like.
And if you run fgfs via the command line with some options, you don’t get troubled by the launcher.


Note the launcher on ‘next’ will be in flux shortly as James wil add some new features - support for the aircraft package manager especially, and for specifying some directory locations to support ‘code only’ nightly builds which use an existing FGData download<ref>http://sourceforge.net/p/flightgear/mailman/message/33503142/</ref>.
Note the launcher on '''next''' will be in flux shortly as James will add some new features - support for the aircraft package manager especially, and for specifying some directory locations to support ‘code only’ nightly builds which use an existing FGData download<ref>http://sourceforge.net/p/flightgear/mailman/message/33503142/</ref>.


However, the upcoming FlightGear 3.6 release is likely to contain an integrated, hard-coded, launcher based on Qt5 to work around this issue (of the mac launcher no longer working)<ref>http://forum.flightgear.org/viewtopic.php?p=228961#p228961</ref>, because James Turner is prototyping a Qt5 cross-platform GUI <ref>http://forum.flightgear.org/viewtopic.php?p=232593#p232593</ref>.
However, the upcoming FlightGear 3.6 release is likely to contain an integrated, hard-coded, launcher based on Qt5 to work around this issue (of the mac launcher no longer working)<ref>http://forum.flightgear.org/viewtopic.php?p=228961#p228961</ref>, because James Turner is prototyping a Qt5 cross-platform GUI <ref>http://forum.flightgear.org/viewtopic.php?p=232593#p232593</ref>.
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/82368"

Navigation menu