Issue 696 in lilypond: Misplaced tuplet number collides with accidental when a kneed beam occurs

[codesite-noreply]

Issue 696: Misplaced tuplet number collides with accidental when a kneed  
beam occurs
http://code.google.com/p/lilypond/issues/detail?id=696

Comment #2 by n.puttock:
If you make the bracket visible, it's easy to see what's causing the bad  
positioning:
though there's usually no bracket in this case, the TupletNumber still  
relies on the
control-points of the bracket to set its position.

The collision is a separate bug; there are a few other issues reporting  
similar
behaviour, reflecting the lack of collision resolution between tuplet  
numbers and
other objects (e.g. slurs, beams and noteheads).

In addition, Eluze's snippet seems to show another problem with kneed  
beams, in that
the spacing is incorrect when there's an accidental: the d and des are too  
close
(this isn't specific to tuplets, as can be seen in the third beat of the  
attached png).

Attachments:
        bugs.png  5.2 KB



--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings