Updates:
Labels: -Priority-Medium -Type-Collision Type-Ugly
Comment #11 on issue 596 by gra...@percival-music.ca: collision tuplet
number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
(No comment was entered for this change.)
___
Comment #10 on issue 596 by d...@gnu.org: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
I don't see where the numerics would originate. What kind of intersection
is supposed to be calculated here? This sounds rather like a home-made
problem where y
Comment #9 on issue 596 by mts...@gmail.com: 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 t
Updates:
Labels: Patch-needs_work
Comment #8 on issue 596 by d...@gnu.org: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596#c8
Patchy the autobot says: Patch does not seem to apply. Discussion
indicates this might need work.
__
Updates:
Status: Accepted
Comment #7 on issue 596 by d...@gnu.org: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
Bug is still there visually and produces the output
Drawing systems...
programming error: no solution found for Bezier intersection
c
Comment #6 on issue 596 by julien.r...@gmail.com: collision tuplet number
and slur
http://code.google.com/p/lilypond/issues/detail?id=596
So is this verified or is this new? Please check.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://
Updates:
Labels: Patch-new
Comment #5 on issue 596 by mts...@gmail.com: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
This is actually a different issue than 307. The problem here is the
polynomial solver leads to numerical inaccuracies for
Updates:
Status: Verified
Mergedinto: -307
Comment #4 on issue 596 by v.villenave: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
Indeed.
--
You received this message because you are listed in the owner
or CC fields of this issue, or beca
Updates:
Owner: ---
Mergedinto: 307
Comment #3 on issue 596 by percival.music.ca: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
Updates:
Status: Duplicate
Comment #2 on issue 596 by percival.music.ca: collision tuplet number and
slur
http://code.google.com/p/lilypond/issues/detail?id=596
Dupe of 307
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you sta
Issue 596: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Defect
--
You received this message because you are listed in the owner
or CC field
Issue 596: collision tuplet number and slur
http://code.google.com/p/lilypond/issues/detail?id=596
New issue report by v.villenave:
% The slur may collide with the tuplet number with following conditions:
% -tuplet is beamed
% -the slur is on the same side as the tuplet number
% -the slur starts
12 matches
Mail list logo
