bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Partcombine bug


From: David Kastrup
Subject: Re: Partcombine bug
Date: Tue, 19 Jun 2012 15:50:00 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.1.50 (gnu/linux)

Rutger Hofman <address@hidden> writes:

> Hello list,
>
> I meet a buglet in partcombine: a slur is drawn across a rest when it
> shouldn't. This happens with 2.15.40 on ubuntu-64bit. The bug doesn't
> occur with 2.14.
>
> I attach a hopefully minimal example.

Since 2.15.40 the following highly relevant commits have happened, so
you might want to retry with current master, or with 2.15.41 once that
is released.  It is likely that your problem is fixed.

commit 8a57f497f6c4f9f00c17040d3c41d30eb2d1b765
Author: David Kastrup <address@hidden>
Date:   Wed Jun 6 15:38:23 2012 +0200

    Issue 2584 (redo 1967): please make partcombine merge slurs
    
    The partcombiner does not really bother about keeping the number of
    generated start and end slur events matched, so this attempts to cope
    by implementing the following behavior:
    
    a) multiple slur starts on the same moment are not an error but the
       same as one.
    b) multiple slur ends on the same moment are not an error but the same
       as one.
    a2) there will be a slur with direction UP if there is at least one
       such start event, and there will be a slur with direction DOWN if
       there is at least one such end event.  This might imply a double
       slur, but for ending it, a single slur end is sufficient.
    
    Consequently, a^(_( c)) (the second closing paren not required, just
    added for prettiness) will add a double slur.

commit 0ed173a51dfd3101e7ef19dc1162bb7f40bbda36
Author: David Kastrup <address@hidden>
Date:   Wed Jun 6 13:12:38 2012 +0200

    Revert "Allow multiple identical slurs (issue 1967)"
    
    This reverts commit b986b38f14195f31e26b0a929c8ac23a8ecfc204.
    
    Conflicts:
    
        lily/slur-engraver.cc


-- 
David Kastrup




reply via email to

[Prev in Thread] Current Thread [Next in Thread]