[Top][All Lists]

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

Re: Fixes NoteColumn vs SpanBar collisions. (issue 5323062)

From: k-ohara5a5a
Subject: Re: Fixes NoteColumn vs SpanBar collisions. (issue 5323062)
Date: Sat, 05 Nov 2011 23:11:45 +0000

>> Pure relevant is used all over the code.
> Good point.  There is even a predicate 'pure-relevant?'
> defining which grobs qualify.

Exactly.  This is how the Pure_from_neighbor_engraver
evaluates which grobs have
pure height functions (line 49).
File lily/ (right):
lily/ SCM pure_relevant_p =
ly_lily_module_constant ("pure-relevant?");
Now, this fills 'items_' with things that pass the 'pure-relevant'
(Since you say Item as opposed to Grob, do you exclude slurs and such?)
lily/ pure_relevants_.push_back
(i.item ());
But 'pure_relevants_' is something different from simply things that
satisfy the predicate 'pure-relevant?'.  It looks like it includes only
items in the immediately-adjacent columns.

This would seems to let accidentals on the second-neightbor-column cross
the extended bar lines. How would this (untested) work?

  \new PianoStaff <<
  \new Staff { R1*4 }
  \new Staff {
    e'1 | \acciaccatura e'16 <e'' cis''' dis'''>4 r2. |
    \slurUp \acciaccatura c''16 <c' fis gis>4 r2.
    <c' fis gis>4 r2.
  } >>

reply via email to

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