Comment #18 on issue 4131 by [email protected]: Patch: Reimplement forced
partcombine decisions via context properties
https://code.google.com/p/lilypond/issues/detail?id=4131
I don't think this is related to the chord range stuff significantly though
as that is more a user interface problem than one of the implementation.
At either rate, I don't think it makes sense to pass the stuff at the
outward level like you do since that makes it impossible to change the
switching ranges within the partcombine. Putting the chord range in a
property would seem to make it reasonably easy to follow the same strategy
for getting the information out from a property as it is done in this patch.
So I think it would most likely make sense to bite the bullet and move to
the property-based stuff. It just extends more logically. And to have
extra commands for "once" is an abomination anyway.
I'm currently stuck in other matters. If this blocks your work, we can
push this as-is (it was in Patch-push anyway) and clean up the
documentation and the regtests at some later point of time to indicate that
not more than one voice should differ from the "automatic" state at any
point of time.
--
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
