Roman Stawski wrote:
The other solution consists of 'adapting' an existing system by adding
or hiding new staves, rather than 'replacing' one system by another one
that's quite different. Your example works in my cut down snippet. In
the full piece, I'd need to add staves above the common one. However,
I can see how to do that by predefining all the staves and using
#(ly:export (skip-of-length ...)) to hide them when they're not needed.
(I see what Mats was getting at now with french staves).
See also how to use alignAboveContext at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond-learning/Nesting-music-expressions
and more explanations of the different alternatives at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Modifying-single-staves#Ossia-staves
By the way, the 4th example of "Ossia staves" may be confusing. There's
no need for any
\startStaff or \stopStaff in this particular example if it instead had
been coded like
<<
\new Staff = ossia \with {
\remove "Time_signature_engraver"
\override Clef #'transparent = ##t
fontSize = #-3
\override StaffSymbol #'staff-space = #(magstep -3)
\override StaffSymbol #'thickness = #(magstep -3)
} \relative c''{R1*3 c4 e8 d c2 }
\new Staff \relative c' {
c4 b c2
e4 f e2
g4 a g2 \break
c4 b c2
g4 a g2
e4 d c2
}
>>
\layout {
\context {
\RemoveEmptyStaffContext
\override VerticalAxisGroup #'remove-first = ##t
}
}
Explaining in detail why the current example in the manual works, is
quite involved.
Anyway, you(ve both given me a practical way forward, and I'll let the
powers that be decide whether the original example constitutes a bug
or an abuse of Lilypond.
Well, we now have a bug report about the problem!
/Mats
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
