Comment #9 on issue 596 by [email protected]: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
I think people thought the patch was arbitrary in its choice of epsilon and I haven't thought of a better solutin since. It's tricky because depending on the epsilon value used the patch may lead to over or under-inclusive avoidance behavior.
People are welcome to take a stab at it - it is an easy fix once someone finds an appropriate epsilon value and/or heuristic for specially dealing with limit values before they can be crunched into numerical-inaccuracy-land.
_______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
