Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • K KConfigWidgets
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Bugzilla
    • Bugzilla
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Frameworks
  • KConfigWidgets
  • Merge requests
  • !133

Merged
Created Apr 25, 2022 by Nicolas Fella@nicolasfellaDeveloper

[kcolorschememanager] Don't save colors on application start

  • Overview 6
  • Commits 1
  • Pipelines 2
  • Changes 1

The KColorSchemeManager ctor loads the saved colorscheme and activates it.

It does that by calling activateScheme(QModelIndex), which calls activateScheme(QString) and saves to the config

The saving is pointless since we are saving the value we just loaded. Instead call activateScheme(QString) directly.

This avoids needless config syncs on startup

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: work/nocolorsaveonload