musescore / musescore/MuseScore

Page number formatting issue (regression since 4.6, worked in 4.5 version)

Open
#33,808 0 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

engraving needs review regression MS4
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

I'm creating a new partition.

I go to Format > Style > Header and Footer (I'm using the French version; I assume that's the correct terminology).
In the right-hand side of the header, I type the code: "$P / $n" to display the page number and the total number of pages on each page.
The page numbers display correctly.

Then I go to Format > Style > Text styles and choose the "Page number" style.
For example I can add Bold effect. It works.
What doesn't work is when I try to add a Frame around the page numbers. The Frame never appears.

One solution that works for putting a border around the text is to use the "Header" Text Format and specify a border. But this is actually a bad solution because I only want to put a border around the page numbers.

Attached, I am sending you my score template in MuseScore 4.5 format, with page numbers in boxes.

PARTITION Modèle [MS] CHORALE.4-5.zip

This bad behavior appeared since version 4.6.
It worked perfectly in version 4.5.
Can you fix this software regression? Thank you.

Supporting files, videos and screenshots

PARTITION Modèle [MS] CHORALE.4-5.zip

In which versions of MuseScore Studio is this issue present?

4.6.1 and next versions

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows 11

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

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.