musescore / musescore/MuseScore
Adding items to a range of staves when some are hidden adds items to all staves and also un-hides them
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
UX/Interaction bug (incorrect behaviour)
Description with steps to reproduce
- Create a score with many instruments (use symphony orchestra template, for example)
- Turn 'Hide empty staves within systems' on
- Let's say you have a system with just a few instruments shown and you want to add the same dynamic to them all; select a range:
- Click a dynamic to add it. It will be added to every stave of the score within the selected range, giving this:
It seems to me more useful to add the new items only to the visible staves in the range. This seems most likely to be relevant to dynamics but possibly to other item types too.
What is the latest version of MuseScore Studio where this issue is present?
4.4.1
Regression
No
Operating system
Any
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
No source file or test is named. Reproduce the issue with the symphony orchestra template and “Hide empty staves within systems” enabled, then trace the range-selection item insertion behavior. Done means adding a dynamic to a range affects only the visible staves and does not un-hide hidden staves; check whether other item types show the same behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100