[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 4169: Line and page breaking syntactic sugar (issue 156400043

From: tdanielsmusic
Subject: Re: Issue 4169: Line and page breaking syntactic sugar (issue 156400043 by address@hidden)
Date: Wed, 22 Oct 2014 10:33:29 +0000

Thanks Keith

On 2014/10/22 05:48:36, you wrote:

Yuck.  The problem seems to be that the override takes effect at the
first beat
in a bar, after the paper-column for the previous barline has been
and the \once makes the override expire before the next bar.

Unfortunately this also means that
   \override Score.NonMusicalPaperColumn.line-break-permission =
only has effect /after/ the R1.

We have a workaround for that timing problem in \overrideProperty, and
\once works fine with

autoLineBreaksOn = {
   \overrideProperty Score.NonMusicalPaperColumn.line-break-permission
   \override Score.NonMusicalPaperColumn.line-break-permission =
#'allow }

autoLineBreaksOff = {
   %?? \overrideProperty
Score.NonMusicalPaperColumn.line-break-permission ##f
   \override Score.NonMusicalPaperColumn.line-break-permission = ##f }

That looks like the way to go.  It seems \once works fine with

I put the %?? because I'm not sure whether it is more intuitive if
should forbid a break before the R1, or mean "here is your last chance
to break,

I prefer "forbid a break before the R1".  That's more consistent with
\autoBreaksOn R1 permitting a break before the R1.  But one drawback is
that placing
\autoBreaksOff before all music in a score gives errors: "bounds of
spanner are invalid".
That's not a problem in practice, but would require a Known issues

I'll post a new patch along these lines.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]