Comment #36 on issue 1698 by [email protected]: Slurs and ties are not
correct over repeats
http://code.google.com/p/lilypond/issues/detail?id=1698
When you say "it is quite clear that you are unwilling to give any
consideration to the actual usability and just want the functionality in.",
I would check out comment #6 and #11 and see how I changed the patch to
make it more useable by taking cues directly from input.
I have posponed pushing this precisely because I care about usability. The
response that I wrote you on Rietveld:
"I like the idea of using BreakSlurEvent and BreakPhrasingSlurEvent because
they
function like BreakDynamicSpanEvent. Essentially, each event that creates a
spanner can have a Break*Event to break said spanner.
This also allows the event to not be a post event, which is important when
you
want to start a score with a broken slur."
which also has an impact on usability, still hasn't been adressed. Take
your time - there is no urgency to push this. What's most important is
that it works on all plans from the internals to the usability.
--
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
