|Subject:||Re: Fixes NoteColumn vs SpanBar collisions. (issue 5323062)|
|Date:||Fri, 11 Nov 2011 16:34:32 +0100|
On Nov 10, 2011, at 7:49 PM, address@hidden wrote:
I posted an uber-patch online that can be separated out into several patches. This uses a new extra-spacing-height for barline to allow span bars to block offending grobs while not applying this to barlines that either don't have span bars or have allow-span-bar set to ##f.
I think that this does everything that needs to be done to fix regressions in addition to adding new functionality that makes sure that accidentals don't shift over/under time signatures, clefs, and key signatures.
After ironing all the kinks out (assuming that there are still kinks to iron out), my plan would be to do the following:
1) Push a patch that fixes the span bar problem.
2) Push a patch that adds extra spacing height to clefs, key signatures, and time signatures to block accidentals from trailing over them.
3) Push a patch that makes the default for LilyPond to block accidentals trailing over barlines.
2 and 3 are still up for debate, but as I've said several times in this thread, there is nothing that i've found in the literature to suggest that music does not work this way.
|[Prev in Thread]||Current Thread||[Next in Thread]|