I have finally tried out the two additional suggestions. Somehow I couldn't
make the one with alignBelowContext work: Lily didn't seem to care whether
I put that in or not, the ossia staff would always end up at the bottom of
the string staff group, below the double bass. Worse, when I put the Violin
II in a StaffGroup, this stuff group would include the violas, cellos, and
double basses below it as well but still put the ossia staff at the very
bottom.


On Fri, Jan 25, 2013 at 7:14 PM, Thomas <trg...@gmail.com> wrote:

> I have finally tried out the two additional suggestions. Somehow I
> couldn't make the one with alignBelowContext work: Lily didn't seem to care
> whether I put that in or not, the ossia staff would always end up at the
> bottom of the string staff group, below the double bass. Worse, when I put
> the Violin II in a StaffGroup, this stuff group would include the violas,
> cellos, and double basses below it as well but still put the ossia staff at
> the very bottom.
>
>
> On Thu, Jan 24, 2013 at 4:18 AM, Mark Witmer <m...@markwitmer.com> wrote:
>
>>
>> Sorry, I forgot that crucial step. You can name a context when you
>> create it:
>>
>> \new StaffGroup = "violinII" \with { ... } { ... }
>>
>> That's the value you can use for alignAboveContext and
>> alignBeforeContext. Thus:
>>
>> \new Staff = "violinIdivisiB"
>>      \with { alignAboveContext = "violinII" } { ... }
>>
>> Here's more information about how to create and name contexts.
>>
>>
>> http://www.lilypond.org/doc/v2.17/Documentation/notation/creating-and-referencing-contexts
>>
>> And more information about context layout order:
>>
>> http://lilypond.org/doc/v2.17/Documentation/notation/context-layout-order
>>
>> I hope that makes more sense!
>>
>> Mark
>>
>
>
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to