Make headers and footers more flexible

Your idea

Make the header/footer functionality more flexible to facilitate a number of common real-world situations.

Problem to be solved

Though there is currently some affordance to have different headers/footers on the first page of a score, it comes down to

• being able to hide the header and/or footer entirely on p1
• being able to indicate that certain items should only be shown on the first page

But this doesn't allow

• for the first page to be anything over than the very first page of the score (e.g. if you have a title page)
• to use the 'first page' header/footer later in the score (e.g. at the start of a new section)
• to show something on the first page but something else on the second page
• any way to alter the header/footer visibility or layout at any point in the score

These problems might be addressed by

• allowing additional header/footer definitions to the default (or at least one extra one, for 'first page style'), and implementing a mechanism for specifying their use on certain pages
• allowing the header or footer of a given page to be edited or overridden or hidden
• a more complete overhaul of the header/footer system (as there are plenty of issues with it beyond what is mentioned here)

One extra point: hitherto, headers from Sibelius files imported via MusicXML have been handled as a vertical frame inserted into the flow at the top of every page. While this reasonably approximates the original, this is nightmarish from a layout point of view, and they ended up littered all over parts, etc - so, when tackling this issue it would be good to also make sure that the Sibelius headers can map to MuseScore headers (and that they are flexible enough to accommodate whatever may be required).

Additional context

This feature request captures point 3 from https://github.com/musescore/MuseScore/issues/14947, which has been closed since the rest of it has been addressed in 4.4.

See also: https://github.com/musescore/MuseScore/issues/17117

Checklist

• This request follows the guidelines for reporting issues
• I have verified that this feature request has not been logged before, by searching the issue tracker for similar requests