Comment #49 on issue 3179 by [email protected]: too few dots in chord (see comment #37)
http://code.google.com/p/lilypond/issues/detail?id=3179

Yes, I think reverting this patch would be the best course.
It does not do what the original requester wanted: "in cases
where a dot would need to be two or more staff spaces
away from the chord" - note "two or more staff spaces"
and "chord" - and it generates incorrect notation in the
more common configurations.

An alternative might be to make the default value
of Score.DotColumn.chord-dots false.  This would then allow
excess dots to be removed on a case-by-case basis without
generating incorrect notation by default for examples like
that in comment 37.

Trevor


--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

Reply via email to