Method loadSettings

kdevplatform/sublime/mainwindow.cpp:331–368

}

void MainWindow::loadSettings()
{
    Q_D(MainWindow);

    qCDebug(SUBLIME) << "loading settings for" << (area() ? area()->objectName() : QString());

    const auto groupName = configGroupName(d->area);
    setStateConfigGroup(groupName);
    const KConfigGroup cg(KSharedConfig::openConfig(), groupName);

    applyMainWindowSettings(cg);

    //debugToolBar visibility is stored separately to allow a area dependent default value
    const auto toolBars = this->toolBars();
    for (KToolBar* toolbar : toolBars) {
        if (toolbar->objectName() == QLatin1String("debugToolBar")) {
            bool visibility = cg.readEntry("debugToolBarVisibility", area()->objectName() == QLatin1String("debug"));
            toolbar->setVisible(visibility);
        }
    }

    d->idealController->loadButtonOrderSettings(cg);

    // applyMainWindowSettings() restores the main window state, including the visibility of ideal toolbars,
    // from config. So the visibility of ideal toolbars may no longer match their emptiness. This can happen if
    // the main window state is out of sync with Sublime::Area's "desired views" config or if some plugin with a
    // tool view is loaded now but was not loaded during the previous KDevelop run (or vice versa) for some reason.
    // Update ideal toolbar visibility to avoid showing an empty toolbar or not showing a nonempty one.
    d->idealController->updateToolBarVisibility();

    if (isVisible()) {
        d->adaptToDockWidgetVisibilities();
    } else {
        d->waitingToAdaptToDockWidgetVisibilities = true;
    }

    d->disableConcentrationMode();
}

void MainWindow::showEvent(QShowEvent* event)
{