Re: [Lilypond-auto] Issue 4052 in lilypond: Document more details on Staff Group Hierarchy

[lilypond]

Comment #1 on issue 4052 by address@hidden: Document more details on  
Staff Group Hierarchy
http://code.google.com/p/lilypond/issues/detail?id=4052

On 04/08/14 18:44, Abraham Lee wrote:> On Mon, Aug 4, 2014 at 11:41 AM,  
David Kastrup <address@hidden> wrote:
> > Abraham Lee <address@hidden> writes:

> >      On Mon, Aug 4, 2014 at 10:39 AM, Richard Shann
> >      <address@hidden> wrote:

> >          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

> >      Well, it's not that other combinations CAN'T be nested at all,
> >      because you've shown that they can. It's just that the
> >      corresponding braces/brackets may not appear like one would expect
> >      them to.

> > No, if they are not accepted, they are created outside of the
> > non-accepting staff.

> Ok. Maybe that could be mentioned somewhere?

> >      Not sure how to clarify this in the docs, but I think this must
> >      also be mentioned somehow. There's something in the behavior of
> >      "\accepts" that still allows them to be present, but the
> >      nomenclature makes it sound like they shouldn't be. Is it must me
> >      or is that a little weird...

> > Here is a diagram.
> > --
> > David Kastrup


> Wow. That's cool, but precisely why I narrowed down my prior nesting  
> tree :)

> Thanks for the clarification!

> -Abraham

Attachments:
        hier.pdf  24.0 KB

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings