At 14:11 on 29 Jul 2016, David Kastrup wrote: >Mark Knoop <[email protected]> writes: >> At 11:26 on 29 Jul 2016, David Kastrup wrote: >>>Mark Knoop <[email protected]> writes: >>>> At 22:09 on 28 Jul 2016, David Kastrup wrote: >>>>>What you are looking for, however, is a >>>>>class of simple omission problems. Maybe we can solve this >>>>>completely differently? Like using "alignAboveContext" being given >>>>>the StaffGroup context name? And just squashing it when the >>>>>StaffGroup to align above is missing? >>>>> >>>>>That would appear to match the problem space well enough again. >>>> >>>> OK, this could be another approach. But this would require a new >>>> property to request this behaviour. >>> >>>I don't see why. Care to explain? >> >> Currently this: >> >> \score { >> << >> \new Staff = "staffone" \with { >> alignAboveContext = "keepstaffonealive" >> \override NoteHead.color = #red >> } { \repeat unfold 120 c'4 } >> \new StaffGroup = "keepstaffonealive" << >> \new Staff = "stafftwo" \with { >> \RemoveEmptyStaves >> \override NoteHead.color = #blue >> } { \repeat unfold 20 c'4 R1*20 \repeat unfold 20 c'4 } >> >> >> \new Staff = "staffthree" \with { >> } { \repeat unfold 120 c'4 } >> >> >> } >> >> keeps staffone alive all the time. The desired behaviour is that >> staffone is only alive while stafftwo is also alive (via the proxy of >> the StaffGroup). If just specifying alignAboveContext kills staffone >> when that context goes away, surely that's a fairly major change of >> behaviour. But perhaps I have misunderstood your approach. > >Hm, so your take is that alignAboveContext is more for establishing >order rather than a connection to the particular named context. Maybe.
The documentation seems pretty clear on this: http://lilypond.org/doc/v2.19/Documentation/notation/context-layout-order http://lilypond.org/doc/v2.19/Documentation/learning/satb-with-aligned-contexts http://lilypond.org/doc/v2.19/Documentation/learning/size-of-objects#index-alignAboveContext-property_002c-example -- Mark Knoop _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
