musescore / musescore/MuseScore
Selection after creating tuplets is inconsistent
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Issue type
UX/Interaction bug (incorrect behaviour)
Bug description
Turning a rest into a tuplet leaves the first rest of the tuplet selected:
Turning a note into a tuplet leaves the first newly-created rest selected:
Turning multiple rests into tuplets (whether via list or range selection) leaves the very first rest selected:
Turning multiple notes into tuplets leaves the first rest after the last note selected:
Ideally this would be consistent, probably so that the first note or rest of each tuplet is left selected.
Equivalent behaviour has been implemented for all other toolbar operations in https://github.com/musescore/MuseScore/pull/20984; this issue has been spun off as it's connected with the gnarly and somewhat distinct matter of tuplet generation.
MuseScore Version
4.3 / master
Regression
No
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.
Assessment
This issue has not been assessed yet.