Settings widget: Make sure initial path is also validated.

Without this patch, validation kicks in only on user input.

Change-Id: I791c45b214e7e171f59c66c7d96f3e85a668427e
Reviewed-by: Nikolai Kosjar <nikolai.kosjar@theqtcompany.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/plugins/clangstaticanalyzer/clangstaticanalyzerconfigwidget.cpp b/plugins/clangstaticanalyzer/clangstaticanalyzerconfigwidget.cpp
index b8fb5cfa47..6bc81cac64 100644
--- a/plugins/clangstaticanalyzer/clangstaticanalyzerconfigwidget.cpp
+++ b/plugins/clangstaticanalyzer/clangstaticanalyzerconfigwidget.cpp
@@ -39,12 +39,12 @@ ClangStaticAnalyzerConfigWidget::ClangStaticAnalyzerConfigWidget(
     chooser->setExpectedKind(Utils::PathChooser::ExistingCommand);
     chooser->setHistoryCompleter(QLatin1String("ClangStaticAnalyzer.ClangCommand.History"));
     chooser->setPromptDialogTitle(tr("Clang Command"));
-    chooser->setPath(settings->clangExecutable());
     const auto validator = [chooser](Utils::FancyLineEdit *edit, QString *errorMessage) {
         return chooser->defaultValidationFunction()(edit, errorMessage)
                 && isClangExecutableUsable(chooser->fileName().toString(), errorMessage);
     };
     chooser->setValidationFunction(validator);
+    chooser->setPath(settings->clangExecutable());
     connect(m_ui->clangExecutableChooser, &Utils::PathChooser::changed,
             [settings](const QString &path) { settings->setClangExecutable(path); });