musescore / musescore/MuseScore
Tablature: Delete/Backspace removes wrong fretmark and note
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Describe the bug
In note input mode, delete or backspace can delete the top note of the chord rather than the one that is selected.
To Reproduce
- Open attached MS4 file (staff + linked tab).
fretmark_delete.mscz.zip - In normal mode, click on a fretmark (not the top one) and press delete.
RESULT: The correct note is deleted.
- UNDO and keep same fretmark selected.
- Enter note input mode.
- Advance one step using the keyboard forward arrow, then go back using the back arrow.
- Press delete.
RESULT: The top fretmark and note is deleted instead of the selected fretmark/note.
Expected behavior
The fretmark selected should always be the one that is deleted.
Platform information
OS: Linux Mint 20.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230290504, revision: c229b14
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
Open the attached fretmark_delete.mscz file in MuseScore and reproduce the deletion sequence in note input mode. Trace the tablature selection and Delete/Backspace handling around the selected fretmark, then verify that the selected fretmark and note—not the top chord element—are removed after navigating forward and back.
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
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100