some elements can get marked invisible, but this doesn't get saved, so is lost on reload

• Sep 17, 2014 - 12:19
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

Brackets, Instrument names are the examples I found so far.
See also #33461: Hidden lines become visible in scores imported from v1.x, these elements too get lost on 1.x import

Comments

• Sep 17, 2014 - 12:19
Title some elements can get marked invisible, but this doesn't get safe, so gets lost on reload ⇒ some elements can get marked invisible, but this doesn't get saved, so is lost on reload

Reply

• Sep 17, 2014 - 15:53

Most likely the answer will be, disable the ability to mark these invisible in the first place. These aren't "real" elements; they are generated on the fly during system layout, since they may change as the number of measures per system changes.

Reply

• Sep 17, 2014 - 17:18

Sort of - I'd just say one buggy behavior is changed into another. In 1.3, you couldn't set just *one* short staff name invisible. If you marked it invisible, it affect that staff for the whole score. At least, it did upon save/reload - at first it looked like you were affecting one system only. That's for exactly the same reason - these aren't "real" (more technical term: persistent) elements. For brackets, it would appear to work, then not survive the reload at all.

Reply

• Sep 17, 2014 - 17:59

Oh, I missed that. Anyway, the 'visible' button in Inspector would need to get disabled for these then, or Inspector should show nothing at all, like for initial barline

Reply