Quoting David Kastrup <d...@gnu.org>:
Small wonder. I thought our default use of symbols matched our naming
rules, but that one's an exception.
We can make an exception for convert-ly here, but that's not a
satisfactorily final solution.
I propose renaming it. Suggestions?
I'm fine with renaming. We have Staff.middleCPosition. Perhaps the
same name could be used in KeySignature.
On the other hand, we don't care where the _middle_ C is positioned.
We only need to know where _some_ C is positioned to decide how to
print the key signature. Then "middle" could be dropped.
By the way, setting KeySignature.c0-position with \override doesn't
work. I had to resort to setting it in Scheme:
\once \override Staff.KeySignature #'stencil =
#(lambda (grob)
(ly:grob-set-property! grob 'c0-position 6)
(ly:key-signature-interface::print grob))
Full example here:
https://gitorious.org/lilypond-music/lilypond-music/blobs/master/Samuel_Barber/The_Daisies.ly
Perhaps c0-position can only be set together with other properties to
have an effect. Or maybe it's not meant to be set. But I need to
change it when I want the key signature to correspond to the staff
clef that is not in effect on the first note (the staff clef is bass,
and the first note is after the treble clef).
--
Regards,
Pavel Roskin
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
