|qmake:||QT += core|
|QFileSelector(QObject *parent = nullptr)|
|QString||select(const QString &filePath) const|
|QUrl||select(const QUrl &filePath) const|
|void||setExtraSelectors(const QStringList &list)|
QFileSelector provides a convenient way of selecting file variants.
QFileSelector is a convenience for selecting file variants based on platform or device characteristics. This allows you to develop and deploy one codebase containing all the different variants more easily in some circumstances, such as when the correct variant cannot be determined during the deploy step.
If you always use the same file you do not need to use QFileSelector.
Consider the following example usage, where you want to use different settings files on different locales. You might select code between locales like this:
QString defaultsBasePath = "data/"; QString defaultsPath = defaultsBasePath + "defaults.conf"; QString localizedPath = defaultsBasePath + QString("%1/defaults.conf").arg(QLocale().name()); if (QFile::exists(localizedPath)) defaultsPath = localizedPath; QFile defaults(defaultsPath);
Similarly, if you want to pick a different data file based on target platform, your code might look something like this:
QString defaultsPath = "data/defaults.conf"; #if defined(Q_OS_ANDROID) defaultsPath = "data/android/defaults.conf"; #elif defined(Q_OS_IOS) defaultsPath = "data/ios/defaults.conf"; #endif QFile defaults(defaultsPath);
QFileSelector provides a convenient alternative to writing such boilerplate code, and in the latter case it allows you to start using an platform-specific configuration without a recompile. QFileSelector also allows for chaining of multiple selectors in a convenient way, for example selecting a different file only on certain combinations of platform and locale. For example, to select based on platform and/or locale, the code is as follows:
QFileSelector selector; QFile defaultsFile(selector.select("data/defaults.conf"));
The files to be selected are placed in directories named with a
'+' and a selector name. In the above example you could have the platform configurations selected by placing them in the following locations:
data/defaults.conf data/+android/defaults.conf data/+ios/+en_GB/defaults.conf
To find selected files, QFileSelector looks in the same directory as the base file. If there are any directories of the form +<selector> with an active selector, QFileSelector will prefer a file with the same file name from that directory over the base file. These directories can be nested to check against multiple selectors, for example:
With those files available, you would select a different file on the android platform, but only if the locale was en_GB.
For error handling in the case no valid selectors are present, it is recommended to have a default or error-handling file in the base file location even if you expect selectors to be present for all deployments.
In a future version, some may be marked as deploy-time static and be moved during the deployment step as an optimization. As selectors come with a performance cost, it is recommended to avoid their use in circumstances involving performance-critical code.
Selectors normally available are
Further selectors will be added from the
QT_FILE_SELECTORS environment variable, which when set should be a set of comma separated selectors. Note that this variable will only be read once; selectors may not
update if the variable changes while the application is running. The initial set of selectors are evaluated only once, on first use.
You can also add extra selectors at runtime for custom behavior. These will be used in any future calls to select(). If the extra selectors list has been changed, calls to select() will use the new list and may return differently.
When multiple selectors could be applied to the same file, the first matching selector is chosen. The order selectors are checked in are:
QT_FILE_SELECTORSenvironment variable, from left to right
Here is an example involving multiple selectors matching at the same time. It uses platform selectors, plus an extra selector named "admin" is set by the application based on user credentials. The example is sorted so that the lowest matching file would be chosen if all selectors were present:
images/background.png images/+linux/background.png images/+windows/background.png images/+admin/background.png images/+admin/+linux/background.png
Because extra selectors are checked before platform the
+admin/background.png will be chosen on Windows when the admin selector is set, and
+windows/background.png will be chosen on Windows when the
admin selector is not set. On Linux, the
+admin/+linux/background.png will be chosen when admin is set, and the
+linux/background.png when it is not.
If supplied, it will have the given QObject parent.
Destroys this selector instance.
Returns the complete, ordered list of selectors used by this instance
Returns the list of extra selectors which have been added programmatically to this instance.
See also setExtraSelectors().
This function returns the selected version of the path, based on the conditions at runtime. If no selectable files are present, returns the original filePath.
If the original file does not exist, the original filePath is returned. This means that you must have a base file to fall back on, you cannot have only files in selectable sub-directories.
See the class overview for the selection algorithm.
This is a convenience version of select operating on QUrl objects. If the scheme is not file or qrc, filePath is returned immediately. Otherwise selection is applied to the path of filePath and a QUrl is returned with the selected path and other QUrl parts the same as filePath.
See the class overview for the selection algorithm.
Sets the list of extra selectors which have been added programmatically to this instance.
These selectors have priority over any which have been automatically picked up.
See also extraSelectors().