Menu
▾
▴
1 Attachments
#415 Hidden accidental of tied note still takes space
Originally created by: *anonymous
Originally created by: wbsoft
%{
A hidden accidental of a tied note still takes space, as visible in
attached PNG, measure 2. As if the accidental is transparent instead of
absent.
%}
\version "2.11.29" % or git as of August 18, 2007
\paper { ragged-right = ##t }
\new Staff \relative c'' <<
{ c2 cis~ | cis c~ | c r } \\
{ c,8 d e d c d e d | c d e d c d e d | c8 d e d [r2] }
>>
Originally posted by: gpermus@gmail.com
This issue has been fixed by 2.11.32.
Status: Fixed
Originally posted by: gpermus@gmail.com
(No comment was entered for this change.)
Status: Verified
Originally posted by: wbsoft
I think the bug is still present in some form, as illustrated below.
\version "2.13.1"
\markup \column {
\line { Here is an interesting bug in both 2.12.0 and 2.13.1. }
\line { This looks good: }
}
\relative c'' {
<ges bes~>2
<fes bes>
}
\markup \column {
\line { But in this case the accidentals removed by }
\line { the tie still take place, as can be seen from }
\line { the distance of the other accidentals. }
}
\relative c'' {
bes1~
<ges bes~>2
<fes bes>
}
Originally posted by: paconet....@gmail.com
The tie is being correctly drawn, and not affected for the ghost accidental as
demonstrated by forcing the accidental:
\relative c'' {
bes1~
<ges bes!~>2
<fes bes>
}
Originally posted by: wbsoft
Yes, the tie is ok. But the accidentals before the ges and the fes are too far to the
left.
Originally posted by: paconet....@gmail.com
I know, I point it only as a possible clue for a solution.
Originally posted by: csnyd...@mvpsoft.com
I did some looking into this recently to see if I could fix it. What I found is that
we have a circular dependency situation: the line-break code needs to know how much
space the accidentals are taking up to know when to insert line breaks, but tied
accidentals will be printed only if the measure is the first measure in the line,
making accidental spacing dependent on line breaks.
When I realized that, I decided that fixing it required more knowledge of the
LilyPond code than I possess. A possible solution I came up with (but do not know how
to implement) would be to have the accidentals take up space when the line breaks are
calculated, but then re-calculate the spacing within each line after deciding where
the line breaks are, removing tied accidentals where appropriate.
Originally posted by: v.villenave
OK, I'm reopening this.
If we are in a chicken-and-egg situation though, I'm not sure it's a good idea to
make LilyPond do the spacing calculation twice (at least, not without a switch that
can disable it by default).
Status: Started
Originally posted by: n.putt...@gmail.com
Wilbert's new example is a separate bug; see issue #612.
This should be tagged fixed_2.11.30.
Originally posted by: v.villenave
Oh, I see. This did ring a bell indeed, but I'm sloppy these days.
Sorry.
Labels: fixed_2_11_30
Status: Verified