Lines: Minimum distance is not saved with score unless it is part of the style

• Sep 21, 2019 - 14:56
Reported version
3.2
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

MS 3.2.3

  1. Open the attached score.
  2. Change the "Minimum distance" for all lines to Zero in the Inspector.
  3. Save and reopen the score.
    Expected result: No change.
    Actual result: The Minimum distances have reset to the style default.
Attachment Size
minimum_distance.mscz 5.77 KB

Comments

• Sep 23, 2019 - 22:35

Well, it works if you change the offset, which is the usual way min distance gets changed. But not if you only change the minimum distance. So not quite as serious as it looked at first. Still, it's an easy enough fix. Just slightly tricky to create a good test for.

Reply

• Sep 30, 2019 - 22:06
Status active ⇒ fixed

Fixed in branch master, commit b995287630

_fix #294728: min distance not saved for lines unless offset changed too

If you move a line into the skyline (e.g, overlapping other elements),
we reduce the min distance automatically and save the result correctly.
But if you reduce the min distance manually via the Inspector
but don't change the offset, then save, the min distance is not written.
That is because we check if the line has been modified before writing these properties.
But we were only checking offset and offset2, not min distance.
This change adds that check._

Reply

Fix version
3.3.0