Wrong Automatic Placement (stacked) of overlapped text elements

• Jul 27, 2018 - 20:11
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Few
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
Yes
Workaround
Yes
Project

All texts below are with automatic placement.
Wrong Automatic Placement.png
Tested in:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (32-bit): 3.0.0, revision: 44debd7


Comments

Title Wrong Automatic Placement Wrong Automatic Placement (stacked) of overlapped text elements

Tried to give better (specific) title

My suggestion for a fix would be a less "greedy algorithm. Currently, we lay out text elements left to right, and if an element intersects the current skyline, it is moved up. What we could consider instead is to "pass" on that element, go on to the next, and if the next can be placed without needing a bump up, then go back to the previous element and autoplace it. This would yield the desired result Isaac's example above - first placing "testing first", then passing on "testing second", then placing "testing third", then going back and placing "testing second".

Complicating this is the fact that different types of text are placed at different times, and this itself is kind of an important aspect (eg, tempo should always be above staff text). But this approach should work well within each type.