Re: Issue 923 in lilypond: chained trills don't always work [redux]

[lilypond]

Comment #1 on issue 923 by n.puttock: chained trills don't always work  
[redux]
http://code.google.com/p/lilypond/issues/detail?id=923

From #670 (and mentioned in the regression test):

3. Trill chains shouldn't overlap horizontally.

Overriding 'padding will tweak the end position, though there's no  
one-size-fits-all
value.

If you want this to happen automatically, that's an enhancement, since the  
line
spanner code does no collision checking at bounds.

The problem for trills is related to the fixed size of the trill element:  
since there
are no spacing rods set, the length of each trill spanner is determined by  
its
bounds.  Since there must always be an integer number of squiggles,  
sometimes the
last glyph is closer to the next trill, which triggers outside staff  
collision avoidance.

I'm not sure what you mean by updating trillspanner-auto-stop.ly.  Your  
snippet has
no automatic stops.

Cheers,
Neil

--
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