* Adjusted validation
* Use default airline object when a color livery is created (refs #774 also)
* Added/improved completer strings (e.g. getVDesignatorDbKey())
* utility functions in lists
* fixed typo in CWebDataServices
* trigger CAirportDataReader::dataRead() when read from cache, too
* make AirportReader part of AllSwiftDbReaders
* fixed typo in CLoginComponent
* use reverse lookup function
* complete model when web services have read the DB data (before that no reverse lookup is possible)
* use new model changed signature
Remark: Temp adjustement when signal allSwiftDbDataRead is sent. As soon #748 is ready needs to be changed to include airport entities
* changed signature of ownAircraftModelChanged to model
* added function for a reverse lookup of a model (string->model) and use it when model changed
* renamed function to updateByLocalFileNames
* simulator info for FS family / as set
* fixed synchronized typo
* info string for caches
* getter for cached models from the loaders
* get all FS family models (FSX/P3D/FS9) from list
Content of this file will follow later to instruct how to properly get
configure and build from source. For now, restore it, since building the
installer requires it to be present.
All model matching will be done simulator independent in
CContextSimulator. The simulator specific part is kept in the model
set.
This also caused the signal modelMatchingCompleted to be renamed to
aircraftRenderingChanged, since the name wasn't accurate anymore.
Both getInstalledModels(), getInstalledModelsCount() and iconForModel()
were removed from the ISimulator interface.
refs #765
On XCB platforms, the initialization of native windows is an async task.
When floating a dock widget, a new top level window is created, followed
by further customizations (changes to title and status bar, child
rearrangements etc). The customizations might be triggered at a time
when Qt was still processing XCB events and the QWindows state not yet
fully initialized. In some random cases, this caused the Window to be
invisible.
By sleeping for 100 ms on XCB platforms, we make sure that
all customizations are delayed long enough that the XCB event thread can
continue to process. By then all XCB communication
should be finished and the window setup complete.
refs #754
