musescore / musescore/MuseScore

Opening or creating a score should automatically close an unedited startup score

Open
#31,275 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Your idea

If you have the 'start with score' option selected, and you create a new score or open an old one in Musescore, your startup score should automatically be closed without a save prompt if it has not been edited.

Problem to be solved

For users who prefer to start Musescore with a blank canvas rather than a new score wizard or the options on Home tab > Scores, the best available course is seemingly to choose 'start with score' and select a template as a startup score. But this setting has an annoying consequence if you start Musescore with the aim of editing an existing score: when you open the old score, your unedited startup score remains open, and when you attempt to close it you are present with a save prompt, even though you never edited it (see issue #24927).

This annoyance is exacerbated by the fact that having the startup score remain open currently means having two instances of MuseScore running (at least in my OS). You definitely don't want an additional score open that you aren't using.

The behaviour I am requesting replicates that of the Microsoft Office applications and probably a lot of modern editing software. It reflects the fact that users will typically open Musescore with the aim of editing an existing score OR creating a new one, not both.

Prior art

No response

Additional context

No response

Checklist
  • This request follows the guidelines for reporting issues
  • I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the startup-score flow and the paths for opening an existing score or creating a new one. The change is complete when an unedited startup score closes automatically without a save prompt in either path, while edited startup scores remain protected.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.