Bad autoplacement of cross-staff accidentals

• May 23, 2019 - 18:17
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
MuseScore

In the attached score, observe that in both examples, one of the two accidentals has been offset to avoid the other accidental (which is in a different voice and on a different staff). The accidental should have better autoplacement.

Attachment Size
Accidental.mscz 5.17 KB

Comments

• May 23, 2019 - 20:26
Priority ⇒ P1 - High

True. I thought at first this might be a regression related to a fix I just made the other day involving notes on cross-staff beams, but it isn't - same result in 3.0.5 and 2.3.2 for that matter.

Not sure if this will end up presenting the same thorny issues to solve as #289498: [Regression] Bad layout of beam in presence of cross-staff beam in another voice. The fix would at least start by separating out the notes in Score::layoutChords3() by virtual staff.

Reply