musescore / musescore/MuseScore
Regression: Save an additional backup even user chose not to save
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
Just as title, an extra safeguard for clicking the wrong button.
(well this FR should have been here like 2 months ago...as said in #19058)
Looks like it's the default behavior of MuseScore 3, there're a bunch of randomly named .mscz in C:\Users\USERNAME\AppData\Local\MuseScore\MuseScore3
Problem to be solved
Current stable (4.1.1) has a wrong button order in saving dialog which should be fixed with #19429, but sometimes I still click the wrong button with correct order dialog in other software, or just carelessly click 'discard' for a draft and instantly get regret, realizing saving it should be better. An additional backup (maybe more) should help in scenarios like this.
Prior art
Microsoft Office do this, most prominently.
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the save/discard behavior described here and the related issues #19429 and #19058. Identify where the save dialog and backup behavior are implemented; the issue provides no file or test names. Done means an additional backup is retained after a user accidentally chooses not to save, with the intended number and retention behavior clarified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100