Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-10 Thread Werner LEMBERG
>> \relative c'' { \override Voice . BendAfter #'after-line-break = #(lambda > > This override doesn't work because the property's called > after-line-breaking. You don't get any warning since LilyPond > (deliberately) does no type checks for grob properties which are set > to procedures or clos

Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-10 Thread Mike Solomon
That does the trick - works like a charm now. Thank you! ~Mike On 7/10/09 6:43 PM, "Neil Puttock" wrote: > 2009/7/10 Mike Solomon : > >> \relative c'' { \override Voice . BendAfter #'after-line-break = #(lambda > > This override doesn't work because the property's called > after-line-breakin

Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-10 Thread Neil Puttock
2009/7/10 Mike Solomon : > \relative c'' { \override Voice . BendAfter #'after-line-break = #(lambda This override doesn't work because the property's called after-line-breaking. You don't get any warning since LilyPond (deliberately) does no type checks for grob properties which are set to proce

Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-09 Thread Mike Solomon
Mark, Thank you - I don't have LilyPondTool, but I will get it. You and I had gone back and forth recently about scheme formatting for LSR submissions - I didn't realize that was a general rule-of-thumb. Sorry for the inconvenience, and thank you for the clean-up (the file compiled on my mach

Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-09 Thread James E. Bailey
On 10.07.2009, at 06:47, Mark Polesky wrote: 5) The \layout block goes *inside* the \score block. Not necessarily, one is global for every \score in a \book, and one only applies to a single \score in a \book. James E. Bailey ___ lilypond-use

Re: difficulty implementing grob-suicide! for spanned bendAfter

2009-07-09 Thread Mark Polesky
Mike Solomon wrote: > Hey lilypond-users, > I am working on a piece with lots of beams/events across > staves, many of which have bendAfter attached to them. The > spanned bend after clashes with some other stuff in the work, so > I wanted to kill it w/ a callback function, but after having >