Re: [Lilypond-auto] Issue 3115 in lilypond: Add convert-ly rule for beam-gap

[lilypond]

Comment #8 on issue 3115 by tdanielsmusic: Add convert-ly rule for beam-gap
http://code.google.com/p/lilypond/issues/detail?id=3115

I'm not so sure reverting is the best course.  The code
fixes the very specific bug of tremolo beams between whole
notes when the second note carries one or two accidentals
by making the beams asymmetric, hence the need for a pair
of numbers rather than one.  If the callback is overridden
with a specific pair of numbers it becomes the user's
responsibility to ensure the beams don't collide with any
accidentals present.  That seems reasonable enough.  I'm not
sure about the hard-wired values, but the jump in the second
beam-gap seems to be required to make a gap when an
accidental is present (?)  Perhaps 'gap could be pressed
back into service to replace the hard-wired 0.8, with 0.8
as its default value?  Then the existing examples would work
correctly again (I think).

Trevor


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings