David Kastrup <d...@gnu.org> writes:
> Actually, if you were using 2.17.6, you could just write
>
> staffdist =
> #(define-music-function (parser location distances)
> (list?)
> #{
> \overrideProperty
> Score.NonMusicalPaperColumn.
> line-break-system-details.alignment-distances
> #distances
> #})
>
> since it was easy enough extending \overrideProperty for dealing with
> subproperties that it would have been pointless not to support them.
Oh, and I'd use number-list? instead of just list? as a predicate. The
more generic your predicate is, the stranger the results for bad uses of
the function will become. If LilyPond sees that some predicate is
wrong, it pulls the plug on the whole function call and substitutes a
dummy value instead. Usually much more straightforward than if a value
gets accepted and problems occur afterwards.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
