As a black text color is enforced for the menu, we should also enforce a
white background for a good contrast.
This is more or less a workaround as this does not respect any system
style settings (dark mode, ...).
This fix will become obsolete once tackling #138 (removing/reducing stylesheet).
Fixes#139
- Mark single argument constructors as explicit
- Remove unused functions
- Avoid default parameters in virtual functions
- Clean up includes
- Do not call static methods through an instance
- And some more...
These methods did not quit the application and hence the application
exits with code -1. Further, when calling swift with a commandline
argument, the user might expect to get a commandline output and not a
GUI popup.
Previously we already switch to loading the bootstrap file only from the
local file (ec42553910).
This removes the remaining parts of loading the bootstrap file from a
remote location.
This also updates the UI in case of parsing errors of the bootstrap.json.
With this, the database debug flag can only be activated when using swift
with a development build. Setting the development flag in the json also
didn't worked previously as expected because the corresponding function
to get the flag in application.cpp was called before the setup was loaded.
The NAV/ field in the remarks (same as COM/) is a freetext field. The content
may be dependent on the air traffic authority/country.
Further, most of the equipment information is nowadays handled with the
ICAO equipment code. NAV/ is likely required in special cases only, for
example when filing equipment code Z (Other equipment).
When using distributed mode and the simulator is already connected to swiftCore, the GUI will not trigger the update on the login component via the simulatorStatusChanged signal.
Therefore we will trigger the initial update manually (same is already done for the simulator connection LED).
