Courtesy time signatures/keys do not disappear if courtesy measure is moved
Reported version
3.0
Priority
P1 - High
Type
Ergonomical (UX)
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
Yes
Workaround
Yes
Project
1) Place time signature/key so that courtesy appears on next system
2) Add/remove adjacent bar so that courtesy measure moves to different system
3) Note that the courtesy signature/key creates a double with the real signature/key
The easiest way to work around this is to disable show courtesy in the inspector yet in Musescore 2 courtesy's would automatically disappear when not needed.
Comments
See also #283177: Insert measure at beginning of system generates extra undeletable key signature., which is a prior report about a related insert issue, and I have a PR to fix that. The issues here issue are probably very similar but my PR doesn't address them, I will see about updating it.
Hmm, actually, now I'm confused, I thought I understood this report but I actually don't. Can you please attach a sample score and more specific steps to reproduce the problem? Eg, have the score you attach already have step 1) done, and then tell us exactly which measure to click before inserting or deleting a measure in order to see a problem.
In reply to Hmm, actually, now I'm… by Marc Sabatella
I believe I'm having the same problem, where the program keeps generating courtesy key signatures randomly when the piece is in one key. I am also looking for a solution. I unchecked the "create courtesy key signature" but, alas my pieces still look like this, in all parts.
(This is an arrangement I'm doing for my senior music seminar class.)
In order to investigate, we need the actual score, not just a picture of it. And ideally, see if you can figure out steps to reproduce the problem - eg, what is the last thing you did before the extra signature appears? But do see the other issue I linked above and see if perhaps it's the same thing - are you inserting measures at the beginning of systems? If so, it's a known issue with a pending fix. But also, be sure you are on the most recent version 3.0.5, as there have been other bugs fixed since the original 3.0 release that could also cause this in some cases.