lilypond-auto
[Top][All Lists]
Advanced

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

Re: [Lilypond-auto] Issue 3338 in lilypond: spacing after 2.17.13 is muc


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3338 in lilypond: spacing after 2.17.13 is much looser
Date: Fri, 03 May 2013 05:34:12 +0000


Comment #13 on issue 3338 by address@hidden: spacing after 2.17.13 is much looser
http://code.google.com/p/lilypond/issues/detail?id=3338

Neither the ossia staff, nor the dynamics line from issue 1669, have any graphical objects at all in the systems where they are having space allowed inconsistently. So there are no stencils to have directional emptiness.

Also, such lines do not 'separate' skylines if there is gap. In general, notes can protrude through a line of dynamics
<<\new Staff {g'4 g' g g'}
  \new Dynamics {s4\p s s s\f}
  \new Staff {\clef bass g4 g' g g} >>

The question is whether the empty line should advance the ideal position of staves to follow, according to the the staff-spacing parameters. Mike and I independently decided empty lines should count for advancing the ideal staff position, but maybe only due to the sneaky way they were being skipped in (some places in) the code. The example of this issue makes it clear that we should *not* advance staff postiions after an ossia staff when it is absent, and skipping the advancement would work for issue 1669 as well, if it is done consistently.

--
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]