musescore / musescore/MuseScore
Position Option Disappears When Selecting Both Dynamics and Hairpins
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
UI bug (incorrect info or interface appearance)
Description with steps to reproduce
- Open/Create any score and place both a dynamic and a hairpin down.
- Select either the dynamic or the hairpin and go to the properties tab and scroll until you see the position property which will be either above or below.
- Then select the hairpin or dynamic also (depending on which on you selected before.) Both the dynamic and hairpin should be selected.
Expected Behaviour:
To see the position property and be able to move both the hairpin and dynamic above or below the staff.
Actual Behaviour:
Position property effectively disappears moving behind the individual options for hairpins and dynamics causing you to have to move the dynamic and hairpin individually.
Supporting files, videos and screenshots
One selected:
Both selected:
What is the latest version of MuseScore Studio where this issue is present?
OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.3.2-241630831, revision: github-musescore-musescore-22b46f2
Regression
No.
Operating system
Windows 11
Additional context
This is a very small issue, maybe even a feature request, but there have been enough times that I've wanted to move both a dynamic and a hairpin (or many of them each) above or below the staff and doing it one at a time is a little annoying, especially because there doesn't seem to be any reason why that couldn't be possible.
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.
Research direction
Reproduce the issue in MuseScore Studio by creating a score with a dynamic and hairpin, selecting both, and checking the Properties tab. Trace the selection and position-property UI behavior; done means the position option remains available and can move both selected elements above or below the staff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100