Multimeasure rest range numbers collide with other elements

• Feb 2, 2021 - 22:20
Reported version
3.6
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project

The new MMRestRange numbers are never added to the skyline, so they can collide with other elements.

1) default score
2) enable mmrests
3) format / style / measure numbers
4) enable the range, set to above placement
5) add staff text, keep typing until it reaches the range numbers

Result: collision


Comments

Status PR created fixed

Fixed in branch 3.x, commit 0c9187491a

_fix #316869: mmrestrange numbers can collide with other elements

Resolves: https://musescore.org/en/node/316869

MMRestRange numbers are never added to sthe skyline,
so text or other elements can and do colldie with them.
Fix is to add these to the skyline.
This commit adds them aloing with measure numbers,
since they otherwise share code with them._

Fix version
3.6.2