Joel Ebel <jbe...@mybox.org> writes:
> On Tue, Aug 25, 2015 at 10:26 PM, Joel Ebel <jbe...@mybox.org> wrote:
>> On Tue, Aug 25, 2015 at 9:53 PM, David Kastrup <d...@gnu.org> wrote:
>>> The following appears to work here. Of course it begs the question
>>> whether we should provide a context definition like that, possibly with
>>> a better name, in LilyPond by default.
>
> Is there a way to get it to stop printing TAB (vertically, in the clef
> space) on subsequent lines after switching to a RhythmicStaff? See
> attached example.
>
> \version "2.19.25"
>
> <<
> \new ChordNames \chordmode {
> c1 c
> }
> \new Line {
> \new TabStaff
> {
> \relative c {
> c4 e g c %\stopStaff
> } %\stopStaff
> } \stopStaff
> \new RhythmicStaff
> {
> 4 8 8~8 8 4 \break
> 4 4 4 4 1
> }
> }
> \relative c' {
> c1 c c c
> }
>>>
>
> \layout {
> \context {
> \name "Line"
> \type "Engraver_group"
> \consists "Axis_group_engraver"
> \accepts TabStaff
> \accepts RhythmicStaff
> }
> \context {
> \Score
> \accepts "Line"
> }
> }
Oh wow. This one is seriously annoying. If you take out all
\stopStaff, it is apparent that the TabStaff is alive through the whole
piece. This is also the case when replacing \new Line with \new
StaffGroup. This is something like the "the first new context in a
group is kept alive" rule. If you replace
\new TabStaff ...
with
<< \new DevNull {} \new TabStaff ... >>
the problem goes away even without \stopStaff. But that's seriously
messed up.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
