Re: Placement of suggested accidentals, with 16th notes

[Mats Bengtsson]

The general principles of moving objects to avoid collisions is 
described in
section "Moving objects". In this specific case, it helps to add
\override AccidentalSuggestion #'padding = #2.0
somewhere before the note.

For the record, I consider it a bug that the padding property is unset 
by default.
I also consider it a bug that LilyPond doesn't check the distance to the 
stem of the
corresponding note, just to the note head, when you set padding.

  /Mats

Richard Oak wrote:
> Hello,
>
> I'm using lilypond 2.10.0 on Windows, and have an 'issue' with the 
> suggestedAcctidentals command. Below is a .ly file that demonstrates the 
> problem:
>
> \version "2.10.0"
>
> bugNotes = \relative c
> {
>         \key f \major
>         \clef bass
>         \time 2/2
>
> 	d16 
> 	\set suggestAccidentals = ##t 
> 	ees 
> 	\set suggestAccidentals = ##f 
> 	a, g a g a bes c8 g e! c |
> }
>
> \score {
>         \context Staff=bug <<
>                 \bugNotes
>         >>
>
>         \layout
>         {
>         }
> }
>
>
> As you can see, the beams and the accidental collide.
>
>
> I cannot find anything in the documentation that covers the placement of the 
> suggested accidental, which is why I consider this a bug!
>
> Any suggestions as to how I get the accidental drawn correctly would be 
> appreciated.
>
>
> Thanks for an otherwise excellent program!!
>
> R
>
>
>
>
> _______________________________________________
> bug-lilypond mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/bug-lilypond
>   

--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================