bug-lilypond
[Top][All Lists]
Advanced

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

Re: Many staff contexts do not nest


From: James
Subject: Re: Many staff contexts do not nest
Date: Tue, 05 Aug 2014 06:58:19 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.0

On 04/08/14 17:39, Richard Shann wrote:
> On Mon, 2014-08-04 at 08:40 -0700, tisimst wrote:
>> On Mon, Aug 4, 2014 at 9:26 AM, David Kastrup [via Lilypond] <[hidden
>> email]> wrote:
>>> Richard Shann <[hidden email]> writes: 
>>>
>>>> The documentation says that staff groups can be nested, but many
>>> don't 
>>>> appear to work, e.g. this 
>>>>
>>>> \version "2.18.0" 
>>>> \score { 
>>>>         << 
>>>>              \new GrandStaff << 
>>>>                                 \new Staff { s1*4/4 } 
>>>>                                  \new ChoirStaff << 
>>>>                                                     \new Staff 
>>>> { s1*4/4 } 
>>>>                                                     \new Staff 
>>>> { s1*4/4 } 
>>>>                                                     \new Staff 
>>>> { s1*4/4 } 
>>>>                                                 >> 
>>>>                              >> 
>>>>         >> 
>>>>     } 
>>>>
>>>> has no GrandStaff. 
>>>> Is something missing at 
>>>>
>>> http://www.lilypond.org/doc/v2.18/Documentation/notation/displaying-staves
>>>> and can anyone explain the rules (I am trying to write a staff
>>> braces 
>>>> checker ...)
>>> #(for-each 
>>>   (lambda (cd) 
>>>    (format #t "~a can accept: ~{~a~^, ~}\n" (car cd) 
>>>     (or (ly:context-def-lookup (cdr cd) 'accepts)))) 
>>>   (ly:output-find-context-def #{ \layout { } #})) 
>>>
>>> -- 
>>> David Kastrup 
>>>
>>> _______________________________________________ 
>>> lilypond-user mailing list 
>>> [hidden email] 
>>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>>
>>>
>>>
>>> ____________________________________________________________________
>>> If you reply to this email, your message will be added to the
>>> discussion below:
>>> http://lilypond.1069038.n5.nabble.com/Many-staff-contexts-do-not-nest-tp165299p165304.html
>>>  
>>> To start a new topic under User, email [hidden email] 
>>> To unsubscribe from Lilypond, click here.
>>> NAML
>>
>>
>> David,
>>
>>
>> Nice solution!
>>
>> Richard,
>>
>>
>> If you'd like to know what the default nesting hierarchy is, you can
>> refer to "engraver-init.ly", which shows this heirarchy of the
>> different contexts that support nesting (recursion removed for
>> simplicity):
>>
>>
>> Score accepts...
>> |- GrandStaff
>> |
>> |- StaffGroup accepts...
>> |   |- GrandStaff
>> |   |- PianoStaff
>> |   |- ChoirStaff
>> |   |- StaffGroup
>> |
>> |- ChoirStaff accepts...
>>     |- GrandStaff
>>     |- PianoStaff
>>     |- StaffGroup
>>
>>
> 
> Perhaps the following could be added to the Nested Staff Groups section
> of the page
> http://www.lilypond.org/doc/v2.18/Documentation/notation/displaying-staves
> 
> "By default Piano Staff, Grand Staff and Staff Group can be nested
> inside a Choir Staff and any of these can be nested inside a Staff
> Group."
> perhaps immediately before the sentence "New nested staff group contexts
> can be defined."
> Thanks for the clarifications, I see what I can reasonably check now.
> 
> Richard
> 

Your wish etc. etc.

http://code.google.com/p/lilypond/issues/detail?id=4052

James




reply via email to

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