Re: Spacing staves with dynamics between; issue 1668 (issue4536088)

[k-ohara5a5a]

On 2011/05/28 07:00:55, joeneeman wrote:
> I'd prefer to leave this comment in
Oops; comments from your last patch are back in.

Re-reading our comments, it is clear that we always want to include
minimum-distances between adjacent lines when computing
get_minimum_translations.  Adjusted patch is up.

The inaccuracy described in your comment happens with lines M v and U
where the v can rattle around between M and U.  We fail to distinguish
the distance between rattling v and U from the actual minimum v-U
distance.  Omitting M-v minimum-distance just gives more room to rattle.

To fix 1442, we needed to ignore only the minimum-distance between
*non*-adjacent already-placed Staffs M and U while distributing
loose-line v.

http://codereview.appspot.com/4536088/