On Mon, 02 Jan 2012 02:41:25 -0800, James <pkx1...@gmail.com> wrote:
@keith and @carl, I see Keith has done something specific for \hidenotes in another patch. Should I use this Tracker (1566) as the Document issue for the @knowissue or for whatever else needs to bedone 'codewise'
Let the documentation patches close issue 1566. Valentin in his original report <http://lists.gnu.org/archive/html/bug-lilypond/2011-03/msg00331.html> thought the beam was hidden by \hideNotes, knew how to get what he wanted, and suggested it might be simply documentation. He tentatively asked for the c8. d16 to be auto-beamed (but in fact it already is). Nobody asked for beams to change properties mid-stroke. So nothing to do 'codewise' in response to 1566. We missed the underlying issue, though. { r8 \once\override NoteHead #'color = #blue \once\override Beam #'color = #blue c'' override Beam #'color = #red c''8. d''16 % These two get auto-beamed in blue } It seems the auto-beamer is thinking about drawing a blue beam starting at the first eight note, changes his mind when he sees the dotted rhythm, but still holds on to the request for blue. If that's a bug, it should be tracked free of the confusion of 1566.
<<attachment: autobeam.png>>
_______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
