Invisible elements should be under visible elements

• Dec 29, 2018 - 15:43
Reported version
3.0
Priority
P1 - High
Type
Functional
Frequency
Once
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project

When you make an item invisible, it is drawn on top of visible items. This make things like shared noteheads invisible. See https://musescore.org/es/node/280786 for discussion in Spanish and picture for example.


Comments

You could change the stacking (or Z-) order in Inspector

And making an element invisible could/might/should do that automatically.
In setting an element invisible, the stacking order filed could get disabled (it only makes sense for visible elementes anyhow) and the stacking value could internally (i.e. without showing that in Inspector) get set to to 0.

I don't think we should actually change the stacking order - unless we promise to restore it (including any user change!) if the element is made visible again. But treating it as 0 makes total sense.

That's what I meant of course, if element not visible, treat as stacking order == 0 and possibly disable the stacking field in Inspetor (but still show the original set value)