20,741
edits
(→The FlightGear executable now checks this: New section) |
|||
Line 33: | Line 33: | ||
== The FlightGear executable now checks this == | == The FlightGear executable now checks this == | ||
This have been added to FlightGear itself by James Turner Jun 21, 2017. FlightGear now checks the property <code>/sim/minimum-fg-version</code> (string) against the FlightGear version and will show some error messages if the aircraft is too new. See {{flightgear source |commit = ec1990 |view = commit |text = this commit}}. | This have been added to FlightGear itself by James Turner Jun 21, 2017. FlightGear now checks the property <code>/sim/minimum-fg-version</code> (string) against the FlightGear version and will show some error messages if the aircraft is too new. See {{flightgear source |commit = ec1990 |view = commit |text = this commit}}. | ||
: I know, see the last change I made at [http://wiki.flightgear.org/index.php?title=FlightGear_Version_Check&diff=108702&oldid=98532]. I don't know how this relates to the other ideas originally discussed on the forum though, and if this also works properly for the non-Qt build, too ? In general, it seems that more and more stuff is added that only works for the Qt-enabled version, whereas the approach used in this article is agnostic to the type of UI in use. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 03:47, 6 August 2017 (EDT) |