Re: New issue: Add StaffAxis context type

[David Kastrup]

tisimst <address@hidden> writes:

> On 8/26/2015 1:14 PM, David Kastrup [via Lilypond] wrote:
>> David Kastrup <[hidden email] 
>>
>> > Perhaps OneStaff?
>
>> \oneVoice _is_ sort of the name for not separating voices vertically.
>
> I can see that, but it still doesn't seem quite right to me. As I've 
> thought about this more, I'm having a hard time understanding what is 
> different about this proposed "StaffAxis" vs. the already defined 
> StaffGroup? It already accepts most other staff contexts, so can we just 
> further add to its capabilities? It seems like all it's really lacking 
> is the "Axis_group_engraver". I haven't tested what you've added to 
> engraver-init.ly, etc., but does it look like this:
>
> %%%%%%%%%%%%%%%%%%%%
>
> \layout {
>    \context {
>      \StaffGroup
>      \consists "Axis_group_engraver"
>    }
> }
>
> \new StaffGroup {
>    \new Staff {
>      c' d' e' f'
>      \chords \with { \override ChordName.Y-offset = -1 } {
>        d1:m7 b1:min7.5-
>      }
>    }
>    \chords \with { \override ChordName.Y-offset = -1 } {
>      d1:m7 b1:min7.5-
>    }
> }

StaffGroup has a Vertical_align_engraver.  It accepts contexts with a
vertical alignment, like StaffGroup itself or GrandStaff.  As a vertical
grouper, it has a Span_bar_engraver.  It has an Instrument_name_engraver
and a System_start_delimiter_engraver.  It's quite a different kettle of
fish.

> I realize that the StaffAxis \accepts more contexts than StaffGroup
> does,

That is probably a shortcoming of StaffGroup.  More important are the
contexts that StaffGroup _does_ accept and StaffAxis doesn't.  And the
multitude of different engravers.

-- 
David Kastrup