musescore / musescore/MuseScore
Toggling visibility of first notehead in tuplet also toggles the tuplet number's visibility
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)
Description with steps to reproduce
- New score
- Select a rest, and add any tuplet
- Inside the tuplet, put at least one note on the very start of the tuplet (i.e. the first thing inside the tuplet bracket should be a note, not a rest)
- Select the head of that first note and press V to toggle visibility of the notehead
- Notice that the tuplet number also becomes invisible even though it wasn't selected, and so does the bracket (if applicable)
Alternatively:
- Set up a tuplet as described above in steps 1-3
- Select the tuplet number and press V to make it invisible
- Select the head of the first note and press V twice
- The tuplet number has become visible again
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/fce093ae-3fc2-4350-8068-403c2edffe12
In which versions of MuseScore Studio is this issue present?
OS: Ubuntu 25.10, Arch.: x86_64, MuseScore Studio version (64-bit): 4.6.5-253511702, revision: github-musescore-musescore-653f38d
Regression
I was unable to check
Operating system
Kubuntu 25.10
Additional context
No response
Checklist
- This report follows the guidelines for reporting bugs and issues
- I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
- I have attached all requested files and information to this report
- I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible
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
Reproduce the issue in a new score using the described tuplet, first-notehead selection, and V shortcut steps. Trace the tuplet, notehead, number, and bracket visibility handling from that interaction; done means toggling the first notehead leaves the unselected tuplet number and bracket unchanged, with coverage for both visibility directions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100