bug-lilypond
[Top][All Lists]
Advanced

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

Re: BendAfter-bugs


From: Simon Albrecht
Subject: Re: BendAfter-bugs
Date: Thu, 24 Dec 2015 13:28:34 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0

Hello Harm,

thanks for reporting.

On 24.12.2015 11:44, Thomas Morley wrote:
While working at
http://lilypond.1069038.n5.nabble.com/note-head-extents-and-event-procedures-tabstaff-td184988.html
I noticed some bugs for BendAfter

%%%%%%%%%%%%%%%%%%%

\version "2.19.32"

%% (1)
%% Collision Accidental/BendAfter
{
   c''2\bendAfter #2
   deses''
}

%% (2)
%% 'minimum-length can't be reasonable applied
%% NR suggest to use:
%% \override Score.SpacingSpanner.shortest-duration-space = #4.0
%% But I'd say that's strange
{
   \override BendAfter #'springs-and-rods = #ly:spanner::set-spacing-rods
   \override BendAfter #'minimum-length = #8
     c''2\bendAfter #2
     d''
}

I conject that (1) will be fixed also if bendAfter is taken into account by horizontal spacing. So I created a single issue, 4711 <https://sourceforge.net/p/testlilyissues/issues/4711/>. In case the fix for (2) should not fix (1), we can easily open a separate issue for (1).


%% (3)
%% input/regression/bend-dot.ly says:
%% "Bends avoid dots, but only if necessary."
%% Though, do we really want this?
{
   e''4....\bendAfter #1
   a''4....\bendAfter #1
}

I agree, that’s ugly. (Both examples, actually, but the first is due to 4711)
<https://sourceforge.net/p/testlilyissues/issues/4712/>


%% (4)
%% A BendAfter tip is printed after line-break
%% But only if line-break happens irregular, i.e. mid-bar or in cadenza
%% issue 1505
%% https://sourceforge.net/p/testlilyissues/issues/1505/
\score {
   \new Staff{
         \cadenzaOn
     c''2\bendAfter #2
     d''\bendAfter #2
     \bar "|" \break

     c''2\bendAfter #2
     \bar "|" \break
     c''2
   }
   \layout { line-width = 60 }
}

%%%%%%%%%%%%%%%%%%%

Added as a comment in 1505.

Yours, Simon



reply via email to

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