Re: Issue 163 in lilypond: huge (ugly) slur (both phrasing and normal)

[lilypond]

Updates:
        Labels: Patch-new

Comment #11 on issue 163 by address@hidden: huge (ugly) slur (both  
phrasing and normal)
http://code.google.com/p/lilypond/issues/detail?id=163

From Mike:

--snip--
Message:
Hey all,

This fixes issue 163.  The only downside is that it adds another entry
to an already-crowded details list.  I also use a magic number of 2
(you'll see a comment about it) that should likely itself either be a
details entry or be taken from an existing details entry.

I agree with Han-Wen's comment in the source that there are too many
properties and that it risks to become unwieldy, so although I like this
patch because it makes a few of my scores look better, I'd like to have
a discussion about consolidating and/or better documenting the details
list in conjunction with the pushing of this patch.  Ideally, I'd like
to see a regtest that clearly demonstrates the utility (and
indispensability) of each entry in the details list.  By constructing
these regtests, it'll likely make pruning the list easier.

Cheers,
MS

Description:
First pass at avoiding very high slurs (fixes issue 163).

Please review this at http://codereview.appspot.com/4817048/