Text frames collide with page numbers.
OS: macOS 10.16, Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548020600, revision: 3224f34
TSIA ("title says it all" — made that up). When a text frame is the first on a page, no matter what you do (i.e., how much "top padding" you ask for, and that's not really a solution), it collides with the page number, and there seems to be no way around it other than to insert another , empty text frame in front of it, which messes up if the pages are re-flowed (when another frame will collide with it instead). This is easily reproducible.
Fixing it will break extant page flows, but it's better to break extant page flows than future ones.
Comments
You know I don't speak English so I might be misunderstanding but, as workaround, have you tried putting some spaces before the lines of text?
In reply to You know I don't speak… by Shoichi
Yes, I have. That's not a solution, but a work-around. It prohibits the paragraph from being re-flowed to the previous page or further down. The vertical region of the page number should not be flowable.
In reply to Yes, I have. That's not a… by [DELETED] 1831606
Another work-around, I don't have any better.
In reply to Another work-around, I don't… by Shoichi
That's actually not so bad. I've never used left/right margin controls on text frames before.... but still, the bug should be addressed.
The issue is that the code for placing the header (which is where the page number lives) places the top of the text relative to the page margin line (which you can if you enable it in the View menu). It's always done this, and never been a good idea, but we got away with it for years because the default for page numbers used to be in the footer. Now that it's in the header, you can indeed get these collisions.
So assuming you want to keep the page numbers in the header, I recommend changing your head text style to use a negative offset, thus pulling the page number higher and leaving your text frame right up against the margin line as it has always been. You could of course also change the margin setting itself in addition.
In reply to The issue is that the code… by Marc Sabatella
Works like a charm. Never knew this capability before. Thanks! (Maybe the default should be changed to -1 line).
In reply to Works like a charm. Never… by [DELETED] 1831606
No doubt it should. As I recall we had a similar issue with footers in the very early days of MuseScore 3 came out that was resolved by adding a 5mm vertical offset to the footer text style, and even then we had compatible concerns, wondering if existing scores that had either depended on this or provided their own workarounds would be adversely affected. Since we now maintain separate pre-3.6 and 3.6 defaults for style settings, we missed an opportunity to keep the old default for header as is but fix this for 3.6. And now, even if there is another 3.x release, it's too late to do something like this without somehow addressing that. So I suspect it will need to wait for MuseScore 4.