lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: repeating bar numbers and rehearsal marks in frenched score


From: David Kastrup
Subject: Re: repeating bar numbers and rehearsal marks in frenched score
Date: Fri, 29 Jul 2016 14:11:42 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)

Mark Knoop <address@hidden> writes:

> At 11:26 on 29 Jul 2016, David Kastrup wrote:
>>Mark Knoop <address@hidden> 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.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]