musescore / musescore/MuseScore
Accessing the menu items lock-down when mouse button is down
@mathesoncalum is already working on this.
Since Jun 6, 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
https://musescore.org/en/node/358245
User cannot do the following:
- Select menu option with [mouse-press]
- Menu manifests (user can also move horizontally to traverse between horizontal options without let-off of button and it will update the view)...
- Position mouse pointer to desired menu item,
- [Mouse-release] to activate the desired option.
Instead in Mu4 the position gets 'locked' unnaturally once pressing a click on mouse (unnaturally in the sense of basing my experience with practically every other program's menus) even when moving around with it down
Is this by design or up for change to be more "normal" or dynamic? Mentioned it back on the forums in the above link back in 2023 but didn't get much of a response... figured I'd post it here to see what the insider team thinks or if it's by design to be this way
Supporting files, videos and screenshots
For example, other apps and MS3 is like so (these are click-and-hold-down actions)
https://github.com/user-attachments/assets/0e51603a-7e4d-4b5d-8d7b-95d858a32c38
MS 4.0 - 4.5 like this (click-and-hold actions):
https://github.com/user-attachments/assets/ec3647cd-2e81-48a5-a726-d1825c6d762a
Also applies horizontally:
https://github.com/user-attachments/assets/baff73c0-ffb4-46de-b176-0b932f99653e
I may have posted about this back in 2022 or so on github, so it might be a double post or a duplicate, but couldn't find anything with a quick search after checking back on the progress of MuseScore 4 Studio. Thanks!
What is the latest version of MuseScore Studio where this issue is present?
4.5.2
Regression
Yes, this used to work in MuseScore 3.x and now is broken
Operating system
Linux w/ XFCE
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.
Assessment
This issue has not been assessed yet.