musescore / musescore/MuseScore
range selection lost on adding section break, if clef change is there
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
- select range selection, which end in place of clef change
- add section break
- see - range selection is lost, clef in next measure is selected instead
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/081c4cd0-905f-4501-b8dd-1329cc5e13fc
What is the latest version of MuseScore Studio where this issue is present?
master nightly
Regression
Yes, this used to work in a previous version of MuseScore 4.x
Operating system
Linux Mint (Ubuntu 22.04)
Additional context
No metter, if courtesy clef is on, or off.
Regression:
Works in 4.0.2
Doesnt work in 4.1.0
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 steps in the master nightly build on Linux Mint, then compare the behavior with MuseScore 4.0.2, where the issue did not occur. The work is done when a range ending at a clef change remains selected after adding a section break, regardless of whether courtesy clef is enabled.
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
- 35/100