Comment #12 on issue 3066 by [email protected]: tie in TabStaff (using q)
displays one of the unisone notes in a chord
https://code.google.com/p/lilypond/issues/detail?id=3066
When fixing the bug introduced in this issue (the loop variable being
incremented too much), the output is the same as before. So reversing the
processing order actually was snake oil here: what was really involved is
that the "fixed" loop skipped half the values, and for this test case
happened to skip a good selection of elements.
Ugh. What's likely a better fix is to stop the loop after the first match
rather than letting the first notehead to tie exhaust all ties.
Reversing the loop might still make sense in that case in order to have
heads matched in order.
--
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
