bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New issue: Add StaffAxis context type


From: tisimst
Subject: Re: New issue: Add StaffAxis context type
Date: Wed, 26 Aug 2015 13:38:32 -0700 (MST)


On 8/26/2015 1:14 PM, David Kastrup [via Lilypond] wrote:
> David Kastrup <[hidden email] 
> </user/SendEmail.jtp?type=node&node=180216&i=0>> writes:
>
> > David Kastrup <[hidden email] 
> </user/SendEmail.jtp?type=node&node=180216&i=1>> writes:
> >
> >> tisimst <[hidden email] 
> </user/SendEmail.jtp?type=node&node=180216&i=2>> writes:
> >>
> >>> I'm not necessarily against it being called "StaffAxis", but I wonder
> >>> if something like "MixedStaff" is more appropriate? Just thinking out
> >>> loud.  I love this idea, btw.
> >>
> >> "StaffAxis" is as appropriate as it gets.  "MixedStaff", however, 
> might
> >> be more suggestive of the typical use case.  I'm a bit skeptical 
> because
> >> it is _not_ a Staff.  But then neither are ChoirStaff or GrandStaff.
> >>
> >> Other ideas would be Squashed (we use that in Pitch_squash_engraver),
> >> Collapsed, CollapsedStaff.  That brings the behavior of the axis into
> >> the name again.
> >>
> >> \new CollapsedStaff
> >> <<
> >>    \new Staff ...
> >>    \new Lyrics ...
> >>    \new ChordNames ...
> >>>>
> >>
> >> seems pretty descriptive, more so than MixedStaff.
> >
> > Perhaps OneStaff?
> >
> > OneStaff to rule them all, OneStaff to find them,
> > OneStaff to bring them all and in the \layout bind them
> > in the scope of \paper where the note heads lie.

Dude! That's awesome! 10 Tolkien points for you!

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

%%%%%%%%%%%%%%%%%%%%



I realize that the StaffAxis \accepts more contexts than StaffGroup 
does, but what do you think?

- Abraham


iibafihh.png (8K) 
<http://lilypond.1069038.n5.nabble.com/attachment/180221/0/iibafihh.png>




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/New-issue-Add-StaffAxis-context-type-tp180204p180221.html
Sent from the Bugs mailing list archive at Nabble.com.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]