Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Steca Steca
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mlzmlz
  • StecaSteca
  • Issues
  • #52
Closed
Open
Issue created Jan 18, 2023 by Wuttke, Joachim@j.wuttkeOwner

Implement new option -f: fresh start, overwriting Steca.conf.

Steca stores numerous state variables in .config/Steca/Steca.conf (under Linux). This can cause difficulties in reproducing reported issues, unless the reporter also provided his Steca.conf. As a remedy, I suggest to implement a new command-line option

    -f   Fresh start, with old configuration moved to Steca.conf.bak

If this option is chosen, then before any call to Qt we call a function from std::filesystem that moves Steca.conf out of the way. Upon that, the GUI should start with default settings.

Assignee
Assign to
Time tracking