Menu

#633 invisibility on rests isn't persistent

Future Release
closed
notation (302)
2
2015-09-18
2004-10-16
No

I'm experimenting with a workaround for |==rests==| taking
advantage of micropositioning, incidentally.

I have an empty, clefless bar ahead of the clef/key. I've marked the
whole rest invisible. Now drag the clef over to this bar, and poof.
It's no longer invisible. At least it no longer appears to be. I
haven't looked at the properties or tried printing it.

This workaround isn't turning out very well, incidentally. It works,
but it looks horrible.

Discussion

  • D. Michael McIntyre

    • assigned_to: D. Michael McIntyre
    • milestone: --> Future Release
     
  • D. Michael McIntyre

    I've been toying with the idea of manually entered rests existing as something like   in HTML, as real, solid, permanent events.

    I may do something with that notion in the nearish future. Maybe.

     
  • D. Michael McIntyre

     
  • D. Michael McIntyre

    I recently got annoyed by this all over again. When working with multiple voices, sometimes you have rests in one part that aren't really necessary for understanding, and you want them hidden. Invisibility on rests is so short-lived it's only good for a couple of load/save/edit cycles before something has messed it up all over again.

    Permanent, fixed rest events seem like a likely solution.

     
  • D. Michael McIntyre

    Or a toggle to "Hide calculated rests" on a per segment basis could work. The only rests in such a segment would be explicitly created rests that serve some real purpose in this voice.

    Hmmm...

     
  • Tito Latini

    Tito Latini - 2015-09-17

    It should be fixed in r14112.

     
  • D. Michael McIntyre

    • status: open --> closed
    • assigned_to: D. Michael McIntyre --> Tito Latini
     

Log in to post a comment.