6/5/2023 0 Comments Flightgear 3.4.0 controls![]() ![]() The fetched files are to be found in $FG_HOME/Aircraft/org.flightgear.* If there are errors related to fetching/using those files, they shoudl show up in $FG_HOME/fgfs.log (look for Catalog.cxx). Thus, the list itself will be populated based on XML files that are automatically downloaded. All the package manager functionality lives in SimGear and is triggered in the form of so called fgcommands. Internally, the launcher is implemented in the form of a Nasal script that resides in $FG_ROOT/Nasal/canvas/gui/dialogs/AircraftCenter.nas using the Canvas GUI APIs and a handful of widgets. The Aircraft Center is primarily written in Nasal and Canvas, as its back-end it is using SimGear http binding for downloading aircraft, and a few fgcommands for dealing with the package manager subsystem. ![]() ![]() Since then, many things have changed - Zakalawe is now working on an integrated Qt5 launcher, which is intended to remain an optional feature, but which is also intended to provide an in-sim replacement for the built-in PUI GUI.Īlso, TheTom is not currently as actively involved as Zakalawe, so that the Aircaft Center has not seen much attention recently - and Zakalawe stated on the devel list that he is now considering the "Aircraft Center" an "experimental feature" that is likely to be deprecated due to this ongoing Qt5 launcher/GUI efforts. The Canvas-based Aircraft Center dialog was originally prototyped by TheTom in response to Zakalawe announcing on the devel list that he was going to come up with a front-end for his still ongoing package manager subsystem, by creating a hard-coded PUI dialog. 3.1 Supporting separate/external Windows for the GUIīackground Note Also see The FlightGear Front-End Situation. ![]()
0 Comments
Leave a Reply. |