musescore / musescore/MuseScore
Issues when entering dynamics by typing
@cbjeukendrup is already working on this.
Since Mar 17, 2025.
- 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
Two related issues.
- Open the dynamics popup by selecting a note and typing Ctrl+D
- Click the left or right arrows in the popup to move to view a different subset of dynamics
- Attempt to type a dynamic into the text box; nothing happens, because focus has shifted to the popup itself.
This works perfectly as intended as long as you have not clicked in the popup.
Secondly:
- Open the dynamics popup by selecting a note and typing Ctrl+D
- Type a dynamic (f, whatever) and press Enter. This creates a line break. Evidently you have to press Esc or click elsewhere to exit edit mode.
Enter should (arguably) do the same as Esc. I'm not saying it should be impossible to have a line break in a dynamics object, but it's an unlikely requirement and could be done in text editing mode. If the user presses Enter, gets the line break and realises they need to press Esc to get out, this has still left them with a dynamics object with a line break at the end (see video) which while not likely to be disastrous, is not ideal either.
https://github.com/user-attachments/assets/344bdcb3-4bd9-42e9-b26c-e70194460b39
What is the latest version of MuseScore Studio where this issue is present?
OS: Arch Linux, Arch.: x86_64, MuseScore Studio version (64-bit): 4.5.0-250721848, revision: github-musescore-musescore-7c55023
Regression
No.
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.
Assessment
This issue has not been assessed yet.