musescore / musescore/MuseScore
Articulation deleted when cut/delete note in chord using selection filter
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
- Create a two note chord
- Add staccato articulation
- Use selection filter to only select top note (same behaviour for bottom note)
- Select the bar (so now one note of the chord is selected)
- Press delete, or cut.
Expected: one note is remaining, with staccato
Actual: one note is remaining, without staccato
Supporting files, videos and screenshots
In which versions of MuseScore Studio is this issue present?
OS: macOS Ventura (13.6.3), Arch.: arm64, MuseScore Studio version (64-bit): 4.7.3-260608135, revision: github-musescore-musescore-cf9860c
Regression
I was unable to check
Operating system
macOS
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
Start by reproducing the issue with a two-note chord, staccato articulation, and the selection filter enabled for one note. Trace the cut/delete path for the selected note and chord articulation handling. Done means deleting or cutting either selected note leaves the remaining note with its staccato articulation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100