On Thu, Sep 16, 2010 at 2:24 PM, Reinhold Kainhofer <reinh...@kainhofer.com> wrote: > I have now implemented overriding the part-combine decisions. For this, I > abuse \set partcombineForced =... events to extract the desired combination > strategy in the \partcombine function (scheme code in scm/part-combine.scm), > before the property_iterator actually gets a chance to set those properties.
General comment (have not looked in detail). If you are not using the actual values, why use properties at all? You could create your own type of event that the part-combiner specifically could look for, and which is ignored for normal processing. Would that not be more natural? -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
