musescore / musescore/MuseScore
Improve UX of saving custom tunings in 'Tunings & temperaments' plugin
Open
Nobody has claimed this yet.
community
plugins
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Follow up from: https://github.com/musescore/MuseScore/pull/28709
Implement improvements to saving over tuning presets and renaming custom tunings. Details in this comment: https://github.com/musescore/MuseScore/pull/28709#issuecomment-3499873135
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 with the linked pull request and its issue comment for the requirements, then locate the “Tunings & temperaments” plugin and trace its saving and renaming flow. Done means the improvements to saving over tuning presets and renaming custom tunings described in that comment are implemented and verified.
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
- Needs clarification
- Newbie friendliness
- 35/100