diff options
| author | David Kastrup <dak@gnu.org> | 2013-09-10 18:22:40 +0200 |
|---|---|---|
| committer | David Kastrup <dak@gnu.org> | 2015-10-05 12:28:52 +0200 |
| commit | dd9cdec4d7fb538b3a201f3b82a10b5ac9ef5f79 (patch) | |
| tree | 1b89f538c0b1ff45bebb2cdccdba61f0a233046e /input | |
| parent | aa2b5b377586a52fcb6b14d4dd464b94f6738560 (diff) | |
Issue 4131/1: Reimplement forced partcombine decisions via context properties
One music type and concept less to worry about.
Since this tracks the partcombine decisions via context properties,
using one forced partcombine override in one voice will not be cancelled
by another forced partcombine in another.
In the event stream, \once\override is indistinguishable from
\override ... \revert so in order to be able to implement
\once\partcombine ... in one voice, we have to retain any permanent
\partcombineForce in the other.
Diffstat (limited to 'input')
| -rw-r--r-- | input/regression/part-combine-force.ly | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/input/regression/part-combine-force.ly b/input/regression/part-combine-force.ly index fda6838ce6..e988e1e1cc 100644 --- a/input/regression/part-combine-force.ly +++ b/input/regression/part-combine-force.ly @@ -1,9 +1,9 @@ \header { texidoc ="Overrides for the part-combiner. All functions like - @code{\\partcombineApart} and @code{\\partcombineApartOnce} are internally implemented - using a dedicated @code{PartCombineForceEvent}. -" + @code{\\partcombineApart} and @code{\\partcombineApartOnce} are + internally implemented using a dedicated @code{partCombineForced} + context property." } \layout { ragged-right = ##t } |