Re: defining new context - alignement issue

[Frédéric Bron]

>>> If you move the Metronome_mark_engraver and Mark_engraver from the
>>> Score context to another context, you also need to move the
>>> Staff_collecting_engraver.
>>
>> I do not understand what it is for but it is clearly better: there is
>> no page break at each end of line.
>
> Both engravers need the stavesFound property (which is maintained by
> the Staff_collecting_engraver) to ensure they're attached to the top
> stave in a system.
>
>>> Clear the MetronomeMark's padding.
>>
>> What do you mean?
>
> The default padding (listed here:
> http://lilypond.org/doc/v2.12/Documentation/user/lilypond-internals/MetronomeMark#MetronomeMark)
> for MetronomeMark is affecting its position; simply override it:
>
> (in your context definition)
>
> \override MetronomeMark #'padding = #0
>
>>> > 2. Also could someone explain the need of \consists
>>> > "Axis_group_engraver" (try to comment it and see that every thing goes
>>> > above the score..., three lines of marks).
>>>
>>> You've answered your own question. :)
>>
>> I still do not understand this and why Stringendo is not on the same
>> line as Lebhaft
>
> If you have a set of graphical elements which are grouped in a line,
> they can't be stacked properly unless they're gathered onto a spanner
> (VerticalAxisGroup) which is created by the Axis_group_engraver (or
> Hara_kiri_engraver, if there are elements which might need to be
> pruned later).
>
> Regards,
> Neil

I just forward your answer to the list for archives.

Frédéric