----- Original Message -----
From: "Neil Puttock" <[email protected]>
To: "Phil Holmes" <[email protected]>
Cc: "Valentin Villenave" <[email protected]>; "LilyPond User Group"
<[email protected]>
Sent: Saturday, November 20, 2010 9:19 PM
Subject: Re: Parenthesised arpeggio collision
On 20 November 2010 13:07, Phil Holmes <[email protected]> wrote:
Looking at this prior to raising a bug report. I'd be interested in
finding
out the actual widths of the arpeggio grobs. Is there a way of printing
these out somehow?
\override Arpeggio #'after-line-breaking =
#(lambda (grob)
(newline)
(display (ly:grob-property grob 'X-extent)))
As a workaround to prevent the collision you can set a tiny amount of
extra-spacing-height:
\override Arpeggio #'extra-spacing-height = #'(-0.1 . 0.1)
Cheers,
Neil
Thanks, Neil. There's definitely something strange about the parenthesis
arpeggio - look what happens when you add padding to all the arpeggio
types - the other ones all move the note to the right, away from the arp,
but the parenthesis moves the arp to the left, away from the notes.
I've reported this: http://code.google.com/p/lilypond/issues/detail?id=1421
--
Phil Holmes
_______________________________________________
lilypond-user mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/lilypond-user
