[Top][All Lists]

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

Re: 2.17.16 vs 2.17.17 Page Breaking

From: Keith OHara
Subject: Re: 2.17.16 vs 2.17.17 Page Breaking
Date: Sat, 04 May 2013 19:21:25 -0700
User-agent: Opera Mail/12.14 (Win32)

On Wed, 01 May 2013 21:34:46 -0700,  wrote:

On Wed, 01 May 2013 21:07:52 -0700, Jay Anderson <address@hidden> wrote:

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
  \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
I do have a '\tempo 4=108' in the score (for midi purposes), but it is
hidden with

I cannot reproduce the full problem.  Has anyone seen LilyPond print 
'annotate-spacing' output where both the limits for the top staff are negative 

When the top staff ends at 0, the commit cited above gives generally better 
page-breaking estimates of the height of the staff (see  
<http://code.google.com/p/lilypond/issues/detail?id=3342>).  The estimate is a 
bit worse in the case where it allows space for a tempo that is completely hidden.  
The reason given for hiding the tempo completely was that it is for midi only, but 
the manual says in that case to use  \midi {\tempo...}

I think I have an implementation of \markLenghtOn that will avoid this problem, 
but if we don't confirm that, then people setting score and parts will space 
the tempo marks in the parts by hand

reply via email to

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