Also, if the score has multiple instruments, and you disable mmrests in a part to make it possible to remove the key sig, when you do remove it and then go to check the score, you will find it was removed from that staff only. That is:
1) new score, flute & oboe, C major, 4/4
2) add E major key signature to bar 7 (anywhere, really)
3) generate parts
4) view flute part
5) turn off mmrests
6) click the key signature
7) delete
8) view score
Result: key signature is removed from flute staff but still present in the oboe staff (and part).
I guess this could be deliberate or not a bad thing in itself, but I thought it worth mentioning.
I can reproduce, and I see exactly the same behavior (impossibility to delete the key sig), in the first scenario (initial message) and in the second one (comment # 1) throughout the past months.
See this result (after final step #8 of the second scenario) on a Nigthly of mid-May: 56177c3
Comments
Also, if the score has multiple instruments, and you disable mmrests in a part to make it possible to remove the key sig, when you do remove it and then go to check the score, you will find it was removed from that staff only. That is:
Ubuntu 14.04, GIT commit: b9e10df
1) new score, flute & oboe, C major, 4/4
2) add E major key signature to bar 7 (anywhere, really)
3) generate parts
4) view flute part
5) turn off mmrests
6) click the key signature
7) delete
8) view score
Result: key signature is removed from flute staff but still present in the oboe staff (and part).
I guess this could be deliberate or not a bad thing in itself, but I thought it worth mentioning.
Maybe see this: #46786: Crash when deleting key signature in part from a GP file
Cross-post.
I can reproduce, and I see exactly the same behavior (impossibility to delete the key sig), in the first scenario (initial message) and in the second one (comment # 1) throughout the past months.
See this result (after final step #8 of the second scenario) on a Nigthly of mid-May: 56177c3
Came up again in #323020: Can't delete key signatures if at mmrest
Workaround is to disable multimeasure rests (temporarily)