New section break inspector lose data

• Dec 25, 2019 - 14:21
Reported version
3.x-dev
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
No
Project
MuseScore

Case 1: Existed Section Break(s)

  1. Find a .mscz file with Section Breaks
  2. Check the properties. This time, it shows the all-good result
  3. Save your file
  4. Reopen it.
  5. Repeat Step 2
  6. The properties all become the default value (3.00s)

Case 2: Section Break(s) with a new-created score ==

  1. Creat a .mscz file with Section Break(s)
  2. Add Section Break(s) to your score.
  3. Check the properties. This time, it shows the all-good result
  4. Save your file
  5. Reopen it.
  6. Repeat Step 3
  7. The properties all become the default value (3.00s).

This file was edited in 3.3.4, developers can use it for testing.

Attachment Size
Transcendental_Etudes_after_Paganini_no._6_in_A_minor.mscz 81.4 KB

Comments

• Dec 25, 2019 - 15:18
Reproducibility Always ⇒ Randomly

I can reproduce on this score but I cannot reproduce on a new score. Can you save that file in .mscx format, delete all things unrelated to the section breaks (to make the file easier to read in text editors) and upload it here?

Reply

• Dec 26, 2019 - 02:29

Correction

Use this file Test.mscz

Case 2: Section Break(s) with a new-created score

  1. Creat a .mscz file with Section Break(s)
  2. Add Section Break(s) to your score.
  3. Check the properties. This time, it shows the all-good result
  4. Save your file
  5. Reopen it.
    Do nothing but Press save again

  6. Repeat Step 3
    The properties all become the default value (3.00s).

Attachment Size
Test.mscz 3.69 KB

Reply

• Dec 26, 2019 - 11:16
Status PR created ⇒ fixed

Fixed in branch master, commit 1b918568d1

_fix #298913: new section break inspector lose data

This is because read() and write() aren't updated to "inspector style" (which deals with Pid instead of variables in class)._

Reply

Fix version
3.4.0