changing score properties via plugin doesn't mark score "dirty"

• Dec 31, 2021 - 08:39
Reported version
3.6
Type
Plugins
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project
MuseScore

1) Open score
2) change score properties via plugin

onRun: {
      curScore.setMetaTag("arranger", "myself")
      Qt.quit()
      }
}

3) score isn't marked dirty

(wrapping in startCmd() endCmd() doesn't work either)

bug - changing score properties via plugin doesn't mark score "dirty"

Comments

• Jan 6, 2022 - 18:02

It is the same in the application. If you change properties the score isn’t marked dirty either. The property page has a concept of dirty and this is set, but it does not flow through to the score itself.

I think the concept of dirty on the score actually comes from whether or not there is anything in the undo stack. Property changes don’t have an undo associated, therefore the score doesn’t think it is dirty.

Question is - should properties be undo-able in which case it may naturally work, or should the concept of dirty change to “undo stack populated or property changed”?

I’m thinking from a UX point of view I’m erring towards the latter otherwise we’d have to open the properties pop up and that might be a bit weird (not to mention getting a bit complex to implement).

I know this issue is about plug-ins not the property screen but I suspect changing the screen behaviour will also correct the plug in behaviour.

Reply