Comment #6 on issue 4131 by [email protected]: Patch: Reimplement forced
partcombine decisions via context properties
https://code.google.com/p/lilypond/issues/detail?id=4131
Well, the screenshots are "as expected" after looking at the corresponding
source code. The example in the manual, in contrast, is unchanged. The
deal here is that previously, you could override a \partcombineApart in one
voice with a \partcombineChords later in a different voice.
Now the point of this issue is that it uses context properties _also_ in
order to implement \once. But "\once" is implemented at the iterator stage.
\partcombineApart ... \once\partcombineChords
in one context is actually indistinguishable at the event level from
\partcombineApart ... \partcombineChords ... \partcombineApart
since \once\partcombineChords first sets the partCombineForced property
to 'chords and restores it to 'apart after the current timestep.
So the basic advice would be not to have more than one part give an
instruction differing from the default \partcombineAutomatic at the same
time, and regtests should likely follow that.
Comments?
--
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
