musescore / musescore/MuseScore
Deleting a staff type change from the first bar in a piece does not reset its properties
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
Engraving bug (incorrect score rendering)
Description with steps to reproduce
Deleting (or otherwise removing, e.g. with Cut) a Staff type change usually causes its properties to be reset so that the staff reverts to the default (or previous) staff type.
This is not the case when deleting a staff type change at bar 1. This persists through reloading the score, and adding a new staff type change at b.1 shows that its properties have been recalled.
Supporting files, videos and screenshots
https://github.com/user-attachments/assets/eeff2327-d7ea-44d7-8c4f-a89c4a246a3b
Reloading score:
https://github.com/user-attachments/assets/d9f6c70c-f9f6-4d2d-b39c-64d4b49c6060
In which versions of MuseScore Studio is this issue present?
Latest 4.7 nightly
Regression
No.
Operating system
Ubuntu 24.04.4 LTS, Windows 11
Additional context
This bug has presented at least since 4.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.
Assessment
This issue has not been assessed yet.