musescore / musescore/MuseScore
Changing first page number no longer immediately updates score
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
Changing First page number in Page > Page settings... no longer updates the score until the dialog is confirmed. Other changes in the dialog (margins, page size, etc.) cause the score to update immediately.
Supporting files, videos and screenshots
4.6.5:
https://github.com/user-attachments/assets/882e52d9-88d1-441f-9054-120590f4ef8f
4.7.0:
https://github.com/user-attachments/assets/fec3e38b-7c8a-4721-b06a-3aa3509f4973
In which versions of MuseScore Studio is this issue present?
4.7.0 - latest main
Regression
Yes, this works in the latest released version and is broken in the nightly builds
Operating system
Ubuntu 24.04.4 LTS
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.
Research direction
Start by reproducing the regression in Page > Page settings... on the latest main build, comparing the First page number field with margins and page size. Trace the dialog's score-update path and determine why this field waits for confirmation. Done means changing First page number updates the score immediately, consistently with the other settings, while the existing confirmation behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100