(look at the tooltip and the --aircraft-dir option in the FlightGear Command window) and
Here follows a more detailed list of the changes in this version:
- Don't hardcode ':' as path list separator for FG_AIRCRAFT and FG_SCENERY. Use os.pathsep instead, which should work better on Windows a least (normally uses ';' since ':' appears in things suchs as 'C:\path\to\foobar'). Having received no single report from users using FFGo to run FlightGear under a non-Linux OS, the only way I can find such portability issues is via code analysis.
- Support use of the FG_AIRCRAFT environment variable. Mix its contents with that of the 'Additional aircraft path(s)' setting from the Preferences dialog, which is mapped to --fg-aircraft. This better reflects what FlightGear does. Detect, log and display in Help -> About the FlightGear version that FFGo is going to run based on the FG_bin setting from the Preferences dialog. Nicer display of the Python version too.
- Hide tooltips when the mouse pointer is moved.
- Tooltip refactoring. New ListBoxToolTip allowing to have a tooltip that depends on the ListBox item under the mouse pointer, using a function of the item index.
- Distinguish between identically-named aircrafts; aircraft tooltips. FFGo stops using only the aircraft name to identify an aircraft. From now on, it uses the aircraft name in combination with the directory containing its -set.xml file. This directory is stored in a new config file parameter (AIRCRAFT_DIR) to allow reliably using the same aircraft between sessions even if there are other aircrafts with the same name in the aircraft paths. The aircraft list now has tooltips showing the aircraft directory, i.e. the directory containing the -set.xml file for the aircraft under the mouse pointer.
Pass the --aircraft-dir option to fgfs (FlightGear) according to the selected aircraft. If the FlightGear version is lower than 3.8, use os.path.realpath() on its value (workaround for the FlightGear bug fixed in commit 7198dec355144fbb0eaccb39f0c241dd07ebaee0, dated October 6, 2015). - New 'aircraftDir' external variable that can be used in the configuration processed by CondConfigParser. This variable contains the selected aircraft's directory.
- Slightly more efficient aircraft search.
- Make sure there is always a selected item in the aircraft list except when it is empty, in particular after doing a search (an aircraft could previously be selected for FFGo but not highlighted in the aircraft list).