Change key signature does not propagate on the other staves if a note or rest is selected

• May 6, 2019 - 13:27
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.6721, revision: 1982daf

1) Open this test file: Test key changes.mscz
2) Measure 9 top staff: select the whole rest -> double-click on D key sig (2#) in the palette

Expected result: all staves receive the change of the new key signature (as in the 2.3.2, or as for a time signature change)
Current result: only the top staff is affected by this change (and Flute part of course)

  • Ditto if instead of double-click, you drag and drog the new key signature on the whole rest (highlighted)

    key sign.jpg


Comments

Title Change key signature does not propagate on the other staves if the rest itself is selected Change key signature does not propagate on the other staves if a note or rest is selected
Priority P2 - Medium

My initial suspicion is that this is actually by design, but a design that should be reconsidered. It's not just a rest in an empty measure - it's any rest, any note. That's because MuseScore actually supports mid-measure key signatures, much like we do mid-measure clefs. As I recall, Werner added that some time ago, and it was never really clear to me why, but I think this is one of the effects.

If we wish to continue to support mid-measure key changes, I would suggest we either make them apply to all staves, or else check rtick() when doing so and if it's zero (fraction), change it to a regular one instead.

If we're going to support mid-measure key changes, then they should work the same as other key changes. You must press ctrl to get the key signature on a single measure.

It seems the current default when less than a measure is selected is a local key signature, and it shouldn't be that way. The user should only get the local mid measure change only when they press ctrl to apply it.

The case in this report should result in all staves getting the new key signature.

yes, all staves should received that mid-measure change, rather than one getting a local signature, that should happen only when Ctrl is pressed too

Yes, that is what I was trying to say, sorry if it was unclear. Right now, all mid-measure key signatures get applied as local, and I don't see a good reason for that. You should need Ctrl to add a local mid-measure key change, just like you need it to create a local "normal" key change.

Priority P2 - Medium P1 - High

As I said, it may be by design to support mid-measure key changes, but it should be reconsidered. At least, for the first note/rest of the measure, we should treat it like the whole measure was selected (add key normally, not locally).