[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.17.16 vs 2.17.17 Page Breaking
From: |
Jay Anderson |
Subject: |
Re: 2.17.16 vs 2.17.17 Page Breaking |
Date: |
Wed, 1 May 2013 21:07:52 -0700 |
On Wed, May 1, 2013 at 12:15 AM, Keith OHara <address@hidden> wrote:
> Nothing was intended to change page-breaking between those versions.
>
> However, almost anything changing layout will change the page-breaking
> when pages are close to full.
>
> If one of these things puts the page-breaking back to the old way
> \markLengthOff
> \override Score.RehearsalMark #'Y-offset = 0
> \override Score.MetronomeMark #'Y-offset = 0
> then something in my change to give space to tempo marks has caused trouble.
(moving to the bug list)
Git bisect led to commit b6f94447415dded7c6e146b41b6139fe76cb84c4
(http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commitdiff;h=b6f94447415dded7c6e146b41b6139fe76cb84c4).
I do have a '\tempo 4=108' in the score (for midi purposes), but it is
hidden with
\layout
{
\context
{
\Score
tempoHideNote = ##t
}
}
When I take out the invisible tempo mark it is set on 1 page again. It
appears that a hidden tempo mark is affecting the spacing somehow. I
haven't had much success creating a minimal example yet unfortunately.
I can probably attempt again this weekend if needed. Thanks.
-----Jay
- Re: 2.17.16 vs 2.17.17 Page Breaking,
Jay Anderson <=