musescore / musescore/MuseScore
[MU4 Issue] Can't move element after escaping from edit mode
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 MS3 you can move a rest, say, by clicking on it and using the up/down arrows. If you then go into edit mode (Alt + Shift + E) you can still use the up/down arrow keys (though in smaller steps). And if you press [Esc] to return to Normal mode you can still move the rest with the arrows (in larger steps again).
However, in MS4, when you press [Esc] in the last step above, you lose the abilty to move the rest.
To Reproduce
- Open any score with a rest in it.
- Click on the rest and use the up/down arrows to move the element vertically.
- Go into Edit mode ( (Alt + Shift + E).
- Again use the up/down arrow keys to move the rest.
- Press [Esc].
- Press the up/down arrow keys.
RESULT: Unexpectedly you lose the ability to move the rest with the up/down arrow keys.
Expected behavior
You should be able to alternate between Normal and Edit mode seamlessly on the same element and retain the ability to move it with the arrows in both cases.
Platform information
OS: Linux Mint 20.1, Arch.: x86_64, MuseScore version (64-bit): 4.0.0-2897153606, revision: github-musescore-musescore-89ef1de
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 MuseScore 4 using the listed Normal/Edit mode sequence and inspect the keyboard handling for the selected rest across the Esc transition. Confirm that arrow-key movement works before entering Edit mode, within Edit mode, and again after returning to Normal mode; no source files or tests are named in the issue.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100