Re: in a \GrandStaff the order of a staff group and a staff can be inversed

[Eluze]

Keith OHara wrote
> Eluze 
> <eluzew <at>
>  gmail.com> writes:
>> 
>> the staff named "last" is engraved /above/ the StaffGroup
> 
> because the StaffGroup is not accepted by a GrandStaff, 
> so is pushed out the bottom, while the Staff is accepted
> in the Staff Group.
> 
> Here we want GrandStaff \with { \accepts StaffGroup } <<>> 
> and this would be a better example for Notation Reference 5.1.7
> http://code.google.com/p/lilypond/issues/detail?id=3641
> 
> I re-opened that issue for documentation because that gives some
> context for why 'acceptance' is not universal.  The people working
> on the code make implicit assumptions that something like a Voice will 
> not contain Staff, and the output is often strange if the assumptions
> are violated.

thank you for explaining this - til now I only thought of these staff
groupers as looking different in a few properties (like connecting bars,
system start symbol ...) but I had not realized they were not mutually
\accepting each other or even staffs

Eluze




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/in-a-GrandStaff-the-order-of-a-staff-group-and-a-staff-can-be-inversed-tp155428p155528.html
Sent from the Bugs mailing list archive at Nabble.com.