Unnecessary space allocated to C major key signature at start of system after key change,

• Mar 3, 2019 - 14:46
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
MuseScore
  1. Download the file below.
    No matter how hard you try to remove "that space" at measure 31, if you save your score, "that space" always ends up being there. It's quite annoying I hope you guys will get rid of this bug ASAP pls.
Attachment Size
TEST 2.mscz 12.32 KB

Comments

• Mar 3, 2019 - 17:43
Title The "invisible keysignature" bug (feel free to judge this title, it's pretty hard to explain anyway). ⇒ Unnecessary space allocated to C major key signature at start of system after key change
Priority ⇒ P1 - High

I would have sworn there was already an issue for this, but I can't find it.

Reply

• Mar 3, 2019 - 17:53
Title Unnecessary space allocated to C major key signature at start of system after key change ⇒ Unnecessary space allocated to C major key signature at start of system after key change,

Worse, if this happens at a place where there already was a line break, and then you delete the break, the key signature disappears entirely.

That is:

1) default score with line breaks every four bars
2) enter a "C" into bar 5 (first bar of second system)
3) add Gb key signature to bar 1
4) add a C key signature to bar 5

Result: as shown, unnecessary space for the C major key signature. This actually disappears on the first relayout.

Then:

4) Delete the system break on measure 4

Result: the key changes disappears completely, but is still present in the score. This too fixes itself on the first relayout.

I'd have called this P0 before the most recent change in our prioritization guidelines, but will leave it as P1 for now.

Reply