lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3631 in lilypond: 2.17 does a worse job with v


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3631 in lilypond: 2.17 does a worse job with vertical spacing and/or the page layout than 2.16
Date: Thu, 24 Oct 2013 18:48:52 +0000


Comment #15 on issue 3631 by address@hidden: 2.17 does a worse job with vertical spacing and/or the page layout than 2.16
http://code.google.com/p/lilypond/issues/detail?id=3631

Comment #6 was about where the bar-numbers are assumed to go to make the height estimates used to break pages.

At the moment, LilyPond tries to place the BarNumber clear of the box-extent of the entire System, then after lines are laid out, places it above the skyline of the top Staff. We can skip that first step by changing the default %\override Score.BarNumber #'Y-offset = #side-position-interface::y-aligned-side
 to
\override Score.BarNumber #'Y-offset = #ly:side-position-interface::y-aligned-side The function without "ly:" is an unpure-pure-container, which changed with issue 3199.

This change should probably be made default for BarNumber MetronomeMark and RehearsalMark. It still includes space for the BarNumbers, etc., but assumes they will sit close to the staff, for purposes of estimating for page-breaks.

This makes annotate-spacing report more accurate heights, and reduces the page count in the example at the top. (There are still smaller differences in page-breaks between version 2.16 and 2.17)

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

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