Re: 2.13.40 regtests

2010-11-25 Thread Han-Wen Nienhuys
On Fri, Nov 26, 2010 at 2:21 AM, Graham Percival wrote: > On Fri, Nov 26, 2010 at 02:15:22AM -0500, Han-Wen Nienhuys wrote: >> The reason I did not do it originally is that it moves the comparison >> farther away from lilypond itself and pixel-per-pixel changes are not >> calibrated for the size o

Re: 2.13.40 regtests

2010-11-25 Thread Graham Percival
On Fri, Nov 26, 2010 at 02:15:22AM -0500, Han-Wen Nienhuys wrote: > The reason I did not do it originally is that it moves the comparison > farther away from lilypond itself and pixel-per-pixel changes are not > calibrated for the size of the symbols: a large symbol moving place > will generate a m

Re: 2.13.40 regtests

2010-11-25 Thread Han-Wen Nienhuys
On Thu, Nov 25, 2010 at 12:45 PM, Phil Holmes wrote: > It wouldn't take me long to write a C# program (less than a day, I'd guess) > that reproduced quite a lot of the regtest checker functionality and did a > pixel-by-pixel check for image changes.  I've done the latter bit in about > 20 minutes

Re: Redefining stencils in 'tweaks causes grobs to be printed twice

2010-11-25 Thread Valentin Villenave
On Thu, Nov 25, 2010 at 1:06 AM, Neil Puttock wrote: > # > # > > When a DynamicLineSpanner is created, it gets its event-cause from the > dynamic grob which triggered its creation: > > 98 Dynamic_align_engraver::acknowledge_dynamic (Grob_info info) > 99 { > 100   Stream_event *cause = info.event_c

Re: Issue 1396 in lilypond: unterminated ties should at least produce a warning.

2010-11-25 Thread lilypond
Updates: Summary: unterminated ties should at least produce a warning. Status: Started Owner: reinhold.kainhofer Labels: -Type-Enhancement Type-Defect Patch Comment #8 on issue 1396 by v.villenave: unterminated ties should at least produce a warning. http://code

Issue 1428 in lilypond: \book cannot contain \bookpart identifier

2010-11-25 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect Priority-Critical New issue 1428 by n.puttock: \book cannot contain \bookpart identifier http://code.google.com/p/lilypond/issues/detail?id=1428 Placing a \bookpart identifier inside \book causes a segfault: \version "2.13.41" mypart = \bookpart

Re: 2.13.40 regtests

2010-11-25 Thread Graham Percival
On Fri, Nov 26, 2010 at 12:14:17AM +, Neil Puttock wrote: > On 26 November 2010 00:00, Graham Percival wrote: > > > Hmm.  It shouldn't take a huge amount of time to compare each pair > > of regtest images -- they're named, so you'd be comparing > > something like 500 pairs of .png images.  (N

Re: 2.13.40 regtests

2010-11-25 Thread Neil Puttock
On 26 November 2010 00:00, Graham Percival wrote: > Hmm.  It shouldn't take a huge amount of time to compare each pair > of regtest images -- they're named, so you'd be comparing > something like 500 pairs of .png images.  (Neil: were you thinking > of something else?) I think this would be very

Re: 2.13.40 regtests

2010-11-25 Thread Graham Percival
On Thu, Nov 25, 2010 at 05:45:36PM -, Phil Holmes wrote: > It wouldn't take me long to write a C# program (less than a day, I'd > guess) that reproduced quite a lot of the regtest checker > functionality and did a pixel-by-pixel check for image changes. Hmm. It shouldn't take a huge amount of

Re: 2.13.40 regtests

2010-11-25 Thread Neil Puttock
On 25 November 2010 17:45, Phil Holmes wrote: > It wouldn't take me long to write a C# program (less than a day, I'd guess) > that reproduced quite a lot of the regtest checker functionality and did a > pixel-by-pixel check for image changes.  I've done the latter bit in about > 20 minutes on the

Re: 2.13.40 regtests

2010-11-25 Thread Phil Holmes
"Neil Puttock" wrote in message news:aanlktim-yd06h47zrvofpp-_qnrm_rwobnfoutokm...@mail.gmail.com... On 24 November 2010 15:47, Phil Holmes wrote: > So if a completely new bit of graphics appears, the regtest checker > wouldn't > spot it? Not sure that's too good. It might not, depending

Re: Issue 1396 in lilypond: Enhancement: an option to turn unterminated ties into slurs

2010-11-25 Thread lilypond
Comment #7 on issue 1396 by reinhold.kainhofer: Enhancement: an option to turn unterminated ties into slurs http://code.google.com/p/lilypond/issues/detail?id=1396 Here's a patch to at least print out a warning and inform the user that a tie could not be created. Otherwise the user will usu

Re: Issue 1055 in lilypond: guile 2.0

2010-11-25 Thread lilypond
Comment #21 on issue 1055 by ianhuli...@gmail.com: guile 2.0 http://code.google.com/p/lilypond/issues/detail?id=1055 Patrick, 1+, but . . . Thinking about this some more, when Guile does its build, how does it register the fact that $GUILE_ROOT_MODULE/ice9/xxx.go is related to $GUILE_ROOT_MODU