- Original Message -
From: "Neil Puttock"
To: "Phil Holmes"
Cc: "Valentin Villenave" ; "LilyPond User Group"
Sent: Saturday, November 20, 2010 9:19 PM
Subject: Re: Parenthesised arpeggio collision
On 20 November 2010 13:07, Phil
On 20 November 2010 13:07, Phil Holmes 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)
(
Cc: "LilyPond User Group"
Sent: Friday, November 19, 2010 5:14 PM
Subject: Re: Parenthesised arpeggio collision
On Fri, Nov 19, 2010 at 5:51 PM, Phil Holmes wrote:
I can't find this on the tracker - is it a known bug? Using parenthesised
arpeggios with 2 (or more) staves, the arpeggio
On Fri, Nov 19, 2010 at 5:51 PM, Phil Holmes wrote:
> I can't find this on the tracker - is it a known bug? Using parenthesised
> arpeggios with 2 (or more) staves, the arpeggio gets too close to the bar
> line when the note values in the other stave are less than full bar. Doesn't
> happen with
I can't find this on the tracker - is it a known bug? Using parenthesised
arpeggios with 2 (or more) staves, the arpeggio gets too close to the bar
line when the note values in the other stave are less than full bar.
Doesn't happen with standard arpeggios.
--
Phil Holmes
<>__
