Lukas Pietsch <lukas.piet...@freenet.de> writes:
> Lukas Pietsch <lukas.pietsch <at> freenet.de> writes:
>
>> Enclosing a reworked patch for review, with the property renamed and the
>> new semantics as discussed.
>
> Sorry, please ignore this one, there were still errors in it. Another
> question: is there a handy type predicate to declare a grob property that
> can take either boolean or integer values, as you guys suggested? I can't
> find a precedent for such a property (there seems to be one that takes
> "boolean-or-symbol?", but no "boolean-or-integer?" so far). If it's too much
> trouble, I guess it might be preferable to drop the idea with the boolean
> values again, as it isn't really that crucial for the intended functionality
> anyway.
Searching for either boolean-or or or-boolean shows that the only
combined predicates are, uh, boolean-or-symbol? and symbol-or-boolean?.
Seriously. Only the first actually has a description in lily.scm, but
the second is used in partcombineForce. Reinhold put it in
ly/music-functions-init.ly and Patrick moved it to c++.scm.
Since it does not have a description, the entry in the notation manual
appendices states
‘partcombineForce’ [music] - TYPE (symbol-or-boolean) ONCE (boolean)
Override the part-combiner.
Ugh. At any rate, we don't seem to have another or-boolean type of
predicate yet. It probably is nicer to stay with numerics, given the
name.
--
David Kastrup
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
