'pizz' and 'arco' text appear above system text
Pizz and arco seem to appear above any system text be default, which seems to be the wrong way round - currently the section title appears below a pizz instruction so the player may miss it.
Is there a way to a) change this around in this case, and b) make the system text appear above everything by default?
Comments
This is on Musescore 3 v3.6.2548021803 and revision 3224f34.
Why would a section title be system text rather than the title text in a vertical frame?
In reply to Why would a section title be… by Jojo-Schmitz
Because it's a continuous score, not a new page for a new movement.
In reply to Because it's a continuous… by GoldmanT
Then it isn't the beginning of a new section ;-)
In reply to Then it isn't the beginning… by Jojo-Schmitz
Could you tell me the correct musical term for the naming that I am using within a piece of music?
In reply to Then it isn't the beginning… by Jojo-Schmitz
Apparently double bar lines indicate the end of and beginning of a section of music, from multiple sources, so a wink back at you. ;-)
In reply to Apparently double bar lines… by GoldmanT
I know what you mean, and don't have a better term than 'section' for it. Maybe what MuseScore calls section should better be called movement, and a section break consequently movement break?
Anyway, below is the answer how to get system trext above staff text
Anyway: If you just enter the staff text (like pizz./arco) first and the system text second, the system text will be above the staff text
In reply to Anyway: just enter the staff… by Jojo-Schmitz
Ah okay so it's just based on the order you enter them? I would have thought system text would default to always being on the top, as it's 'global' information rather than 'local', but I can work around that.
In reply to Ah okay so it's just based… by GoldmanT
Indeed a bit counter-intuitive
In reply to Ah okay so it's just based… by GoldmanT
Staff and system text are - or were, anyhow, when this was first implemented - the same element type internally. So that's why it's first-come, first-served - that's how it works for elements of the same type.
Probably this should be special-cased to make sure system text does always come out on top, because I agree, it probably makes sense more often than not.