Staff space changed without reason when opening a MuseScore3 file.

• Jun 22, 2020 - 14:42
Reported version
4.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
needs info
Regression
No
Workaround
No
Project
MuseScore

1) Open a MuseScore3 file (e.g. beam-shift.mscz).
2) Select a note.
3) Deselect the note by clicking somewhere outside the measure.

Expected behavior:
Note deselected.

Observed behavior:
Note deselected and score changed.

Attachment Size
beam-shift.mscz 2.62 KB

Comments

• Jun 22, 2020 - 14:47

The Score Comparison Tool, comparing the current with the last saved version, shows spatium is changed from 1.76389 in the original file into 1.764, which is on the inspector.

Reply

• Jun 22, 2020 - 18:35

I know that discussion, had a look into it myself too. It seems to me the main issue here is the QDoubleSpinBox which, at least for me, has a fundamental flaw. You can put any any double into the widget but it isn't storing the double as a double but as a string. So, when retrieving the value, you will get a, slightly, different value, even when nobody actually changed the value. In my professional life we had a lot of problems with this, causing unstable results, flipping between two values.

I didn't had a look into this particular issue yet but it might the new model/view approach could be our rescue. Just save the data in the original format and use a different display value (the string). This solves the flaw in the spinbox.

Reply

• Jun 30, 2020 - 20:04
Title Staff space changed with reason when opening a MuseScore3 file. ⇒ Staff space changed without reason when opening a MuseScore3 file.

Reply

• Jan 11, 2022 - 14:13
Status active ⇒ needs info

I am unable to reproduce this on a 2022-01-10 4.x nightly on macOS. Can you verify if the issue still exists for you? If not, we can close it.

Reply