[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Lilypond-auto] Issue 2932 in lilypond: Patch: Change \alterBroken i
From: |
lilypond |
Subject: |
Re: [Lilypond-auto] Issue 2932 in lilypond: Patch: Change \alterBroken interface to match that of other tweak/overrides |
Date: |
Tue, 30 Oct 2012 22:27:01 +0000 |
Updates:
Status: Fixed
Labels: -Patch-countdown Fixed_2_17_6
Comment #6 on issue 2932 by address@hidden: Patch: Change \alterBroken
interface to match that of other tweak/overrides
http://code.google.com/p/lilypond/issues/detail?id=2932
This has been pushed to staging as part of the issue 2934 push, partly
inside of a merged side branch involving an update-with-convert-ly run.
The commit relevant to this issue in particular are:
commit 54f7187cb95349fb08d359d36b0105ecaa102d15
Author: David Kastrup <address@hidden>
Date: Sat Oct 27 21:08:17 2012 +0200
Change input/regression/alter-broken.ly to include tweak-like usage
Also change override-like usage for ties to \once\alterBroken as the
control point manipulations are unlikely to be desirable for more than
a single occurence.
commit 13da8b27aabc5d5a752d00ed1e2b99ad20f0f264
Author: David Kastrup <address@hidden>
Date: Mon Oct 29 16:25:02 2012 +0100
Rerun scripts/auxiliar/update-with-convert-ly.sh
commit ec6b407a65c6da5a41fe2e3d250d67a20ee65e15
Author: David Kastrup <address@hidden>
Date: Sat Oct 27 17:21:54 2012 +0200
Change \alterBroken interface to match that of other tweak/overrides
commit 2188505a75fb36893b0ec261c6bc194a201ec66e
Author: David Kastrup <address@hidden>
Date: Thu Oct 25 14:42:25 2012 +0200
Implement function check-grob-path for checking/extending grob path
specs
From the function documentation string:
Check a grob path specification @var{path}, a symbol list (or a
single symbol), for validity and possibly complete it. Returns the
completed specification, or @code{#f} if invalid. If optional
@var{parser} is given, a syntax error is raised in that case,
optionally using @var{location}. If an optional keyword argument
@code{#:start @var{start}} is given, the parsing starts at the given
index in the sequence @samp{Context.Grob.property.sub-property...},
with the default of @samp{0} implying the full path.
If there is no valid first element of @var{path} fitting at the given
path location, an optionally given @code{#:default @var{default}} is
used as the respective element instead without checking it for
validity at this position.
The resulting path after possibly prepending @var{default} can be
constrained in length by optional arguments @code{#:min @var{min}} and
@code{#:max @var{max}}, defaulting to @samp{1} and unlimited,
respectively.