musescore / musescore/MuseScore
[MU4] Inconsistent behavior with the fine adjustment of elements on the score
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
Other
Bug description
Back in Musescore 3.6, using the keyboard arrows to finely adjust the position of any manipulable element (including anything that possessed manipulation handles) on the score resulted in said element being moved by increments of 0.1sp. In Musescore 4, this behavior seems to be inconsistent between different types of objects.
For certain objects (any ornament such as dynamics, coda signs, trill marks and text for instance), using this fine tuning method still results in adjustments by increments of 0.1sp, whereas for others (namely for any object fine-tunable using handles, such as lines, slurs or hairpins), increments of 0.5sp are applied, which are way too big for a fine adjustment. The old behavior of adjusting everything by increments of 0.1sp when using the keyboard arrows (especially for manipulation handles) should be reinstated.
Moreover, it shall be noted that every single object of the "Breaths and Pauses" palette is not adjustable anymore by using the keyboard arrows, which seems to be a bug given that it was previously possible.
Steps to reproduce
For the handle-adjustable objects:
- Create a arbitrary new score
- Insert a few notes
- Create a slur (or hairpin, or arbitrary line) between the first and last note
- Click on the created object and select one of the handles, then try to adjust it with the keyboard arrows (having the inspector opened on the Appearance sub-menu shows adjustments by increments of 0.5sp)
For the Breaths and Pauses objects:
- Add a few more notes to the previous score
- Select a note and add any symbol from the "Breaths and Pauses" palette
- Select the added object and try to move it with the keyboard arrows
Screenshots/Screen recordings
No response
MuseScore Version
4.0.2.230651546
Regression
Yes, this used to work in Musescore 3.x and now is broken
Operating system
macOS 10.15.7
Additional context
OS: macOS 10.15
Arch.: x86_64
MuseScore version (64-bit): 4.0.2-230651546
revision: github-musescore-musescore-dbe7c6d
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.