tisimst <tisimst.lilyp...@gmail.com> writes:
> Dimitris,
>
> On Saturday, July 2, 2016, dtsmarin [via Lilypond] <
> ml-node+s1069038n192107...@n5.nabble.com> wrote:
>
>> Thank you, but this is not what I'm looking for.
>> I want a special type of "Engraver_group" like Staff, GrandStaff etc.
>> e.g.
>> scoreAViolaPart = \new GrandStaff \with { \clef "alto"
>> } << \set GrandStaff.systemStartDelimiter = #'SystemStartSquare
>> \new Staff = "A" << \global \scoreAViolaAI \\ \scoreAViolaAII >>
>> \new *HiddenStaff* = "B" << \global \scoreAViolaBI \\ \scoreAViolaBII
>> >>
>> >>
>>
>> This way, the command \RemoveEmptyStaves will only affect the HiddenStaff
>> staves, that will have by default this command enabled.
>>
>> I hope this makes sense.
>>
>
> Maybe all you need is :
>
> \new Staff \with { \RemoveAllEmptyStaves } {...}
I cannot figure out at all what the original poster wants. If your
proposal is in any way going in the direction he is aiming for, chances
are that
\layout {
\context { \Staff
\name "HiddenStaff"
\alias "Staff"
\RemoveAllEmptyStaves
}
\inherit-acceptability HiddenStaff Staff
}
will do what he wants with regard to an additional HiddenStaff context
(though I have no idea why one would use that name, and one may want to
do the same for \midi though without \RemoveAllEmptyStaves in order to
not have the Midi production confused by HiddenStaff).
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
