On 2015/06/27 19:45:12, thomasmorley651 wrote:
bassStaffProperties and trebleStaffProperties are not really
documented, though
I'd call it more a documentation issue.
...
I vote for keeping them, although I think it's a very cumbersome
method to
specify which clefs the PianoStaff should use.
If one follows the NR's suggestion to instantiate staves explicitly,
your example is transformed into something more lilypondish (below).
Removing these properties will make it easier for me to consolidate some
code for \autochange and \partcombine.
\version "2.19.0"
\score {
\new PianoStaff <<
\context Staff = "up" \with {
clefGlyph = "clefs.C"
clefPosition = 0
middleCPosition = -5
middleCClefPosition = -5
} {
\new Voice = "melOne" {
\autochange {
g4 a b c'
d'4 r a g
}
}
}
>>
}
https://codereview.appspot.com/249970043/
_______________________________________________
lilypond-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-devel
