Stacking order, autoplace not saved for generated stems

• Dec 2, 2018 - 16:11
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Many
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
MuseScore

In MuseScore3 beta, I found that MuseScore didn't keep the value of Stacking order of STEMS when I changed the value.
I changed the value from 1800 to 3000 at the stacking order of STEMS in Inspector and saved the file, and then I opend the file, I found the value was rewrited to 1800.

Comments

• Dec 2, 2018 - 16:44
Status active ⇒ by design

when you change the note's value (pitch, duration?) you effectivly rewrite it, including the stem, so it is a new stem and as such uses the default stacking order

Reply

• Dec 2, 2018 - 17:30
Title Stacking order for stem not saved ⇒ Stacking order, autoplace not saved for generated stems
Workaround No ⇒ Yes
Priority ⇒ P2 - Medium

I can confirm. Stems are normally considered "generated" elements, meaning we don't save information about them unless you have customized them. We do this if you've changed anything else - visibility, length, etc - but we don't for stacking order. Also, seems we don't for "automatic placement". But oddly, this doens't apply to all generated elements, it works fine for clefs for example.

Workaround - change anything else about the stem to force it to be considered non-generated (eg, lengthen it by 0.01sp).

Reply

Fix version
3.1.0