Updates:
Status: Verified
Comment #23 on issue 307 by brownian@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
___
bug-lilypond mailing
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_15
Comment #22 on issue 307 by tdaniels...@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Mike says: [Fixed] by increasing the slur region based on the height of the
Updates:
Labels: -Patch-countdown Patch-push
Comment #21 on issue 307 by colinpkc...@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Cou8nted down to 20111009 and it's great to see such an ancient bug getting
swatted!
Updates:
Labels: Patch-new
Comment #18 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307#c18
Sketch for fix of issue 307
http://codereview.appspot.com/4813048
___
Updates:
Status: Started
Owner: mts...@gmail.com
Cc: lemzw...@googlemail.com
Labels: -Patch-new Patch-review
Comment #17 on issue 307 by pkx1...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Passes make
Updates:
Labels: Patch-new
Comment #16 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307#c16
Sketch for fix of issue 307
http://codereview.appspot.com/4813048
___
Updates:
Labels: Patch-new
Comment #13 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307#c13
Sketch for fix of issue 307
http://codereview.appspot.com/4813048
___
Updates:
Labels: -Patch-new Patch-needs_work
Comment #15 on issue 307 by pkx1...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Passes make but fails make check
--snip--
job 4 terminated with signal: 6
job 3 terminated with
Updates:
Labels: -Patch-countdown Patch-push
Comment #12 on issue 307 by colinpkc...@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Counted down to 20110928
___
bug-lilypond mailing
Updates:
Labels: -Patch-review Patch-countdown
Comment #11 on issue 307 by colinpkc...@gmail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
___
Updates:
Labels: -Priority-High -Patch-needs_work Patch-new
Comment #9 on issue 307 by percival.music.ca: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
needs checking.
___
bug-lilypond mailing
Updates:
Labels: -Patch-new Patch-review
Comment #10 on issue 307 by pkx1...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Passes make and reg tests
___
bug-lilypond mailing list
m...@apollinemike.com m...@apollinemike.com writes:
Between the two options attached, which one is better? I like the
first...but I'm the contemporary music attaché and know nothing about
how normal music is supposed to look :)
Both of them use:
\relative c' {
\override Slur #'details
@gnu.org
Subject: Re: Issue 307 in lilypond: collision slur with tuplet bracket
Between the two options attached, which one is better? I like the first...but
I'm the contemporary music attaché and know nothing about how normal music is
supposed to look :)
---
Shouldn't the slur be 'down
Between the two options attached, which one is better? I like the
first...but I'm the contemporary music attaché and know nothing about
how normal music is supposed to look :)
The first, perhaps with even more slur curvature to make the distance
to the the corner of the tuplet bracket more
Updates:
Labels: Patch-new
Comment #6 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Patch at http://codereview.appspot.com/4813048.
___
bug-lilypond mailing
Updates:
Labels: -Patch-new Patch-needs_work
Comment #7 on issue 307 by pkx1...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
___
Comment #4 on issue 307 by mts...@gmail.com: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
What would be the ideal output in this case? Should the tuplet bracket and
number be moved up, should the slur end higher, or should the tuplet
bracket
Comment #5 on issue 307 by lemzw...@googlemail.com: collision slur with
tuplet bracket
http://code.google.com/p/lilypond/issues/detail?id=307
For my test case, I suggest to position the `more local' context next to
the staff. Thus I would like to have the tuple bracket unchanged, and the
Comment #3 on issue 307 by percival.music.ca: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
Issue 596 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
Updates:
Labels: -Priority-Medium Priority-High
Comment #2 on issue 307 by percival.music.ca: collision slur with tuplet
bracket
http://code.google.com/p/lilypond/issues/detail?id=307
(No comment was entered for this change.)
Attachments:
foo.preview.png 2.3 KB
--
You
21 matches
Mail list logo
