|
From: | lilypond |
Subject: | Re: [Lilypond-auto] Issue 4131 in lilypond: Patch: Reimplement forced partcombine decisions via context properties |
Date: | Fri, 10 Oct 2014 04:55:09 +0000 |
Comment #12 on issue 4131 by address@hidden: Patch: Reimplement forced partcombine decisions via context properties
https://code.google.com/p/lilypond/issues/detail?id=4131I don't understand #11, but I see what the patch is doing now. The advice I quoted in #10 isn't correct.
\partCombineAutomatic is implemented as an unset, so it is passive, so in the two changed regtests when one part says \partCombineApart and later the other part says \partCombineAutomatic, the \partCombineApart wins.
The new behavior is consistent with the documentation, and could be clarified with "\partCombineAutomatic ... and revert back to the standard \partcombine functionality, unless one of the earlier commands remains in force in the other part being combined."
Alternatively, to keep current behavior, \partCombineAutomatic could be implemented as a \set to 'automatic so it is heard and acted on by the \partcombine function.
--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
[Prev in Thread] | Current Thread | [Next in Thread] |