Updates:
Status: Verified
Comment #6 on issue 1792 by brownian.box: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Comment #5 on issue 1792 by k-ohara5...@oco.net: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
With the fix above for this issue, the behavior matches the documentation.
"prefer-dotted-right (boolean) : For note collisions, prefer to shift
dotted up-note to t
Comment #4 on issue 1792 by n.putt...@gmail.com: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
Did I miss the countdown for this?
Why does the second beat still look bad even with prefer-dotted-right =
#t? The lower voice's dot looks as if it's attached to th
Comment #2 on issue 1792 by k-ohara5...@oco.net: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
the reg test 'before' was different
As part of the patch, I needed to expand the regression test.
I used the expanded test as the bug report. The before/after outpu
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1792 by pkx1...@gmail.com: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
Passes make and reg tests although in my case, the reg test 'before' was
different - see attached:
Not sure why this
Status: Started
Owner: k-ohara5...@oco.net
Labels: Type-Collision Priority-Medium Patch-new
New issue 1792 by k-ohara5...@oco.net: dot-notehead collision
http://code.google.com/p/lilypond/issues/detail?id=1792
%% Dots should move where we can see them,
%% or, if dots need to move and we ask for
