[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 879 in lilypond: RemoveEmptyStaffContext doesn't need to disab
From: |
lilypond |
Subject: |
Re: Issue 879 in lilypond: RemoveEmptyStaffContext doesn't need to disable auto-knee-gap |
Date: |
Wed, 05 Jan 2011 16:34:20 +0000 |
Comment #2 on issue 879 by PhilEHolmes: RemoveEmptyStaffContext doesn't
need to disable auto-knee-gap
http://code.google.com/p/lilypond/issues/detail?id=879
Not sure what a regtest would look like. What we're trying to do is show
that removing \override Beam #'auto-knee-gap = #'() from the definition of
RemoveEmptyStaves doesn't break something else. The only thing I can think
of here would be a regtest that showed the knee being properly placed.
Note that this would now have to use a StaffGroup not a PianoStaff, since
empty PianoStaff's are no longer removed now Issue 442 has been fixed.
Attached is a possible regtest (without description) and image of its
appearance.
Attachments:
RemoveEmptyBug.ly 582 bytes
RemoveEmptyBug.png 13.3 KB
- Re: Issue 879 in lilypond: RemoveEmptyStaffContext doesn't need to disable auto-knee-gap,
lilypond <=
Re: Issue 879 in lilypond: RemoveEmptyStaffContext doesn't need to disable auto-knee-gap, Keith OHara, 2011/01/05