2011/2/14 Keith OHara <k-ohara5...@oco.net>:
> The override below makes the spring stiff enough to avoid this extra check,
> so the spring near the accidental is not lenghened. (The override will not
> work well in tight layouts.) Does this produce closer to what the good
> engravers do?
> -Keith
>
> \score{{
> c''1 \break
> c'4 d' g' f' e'2 a' d'1 \break
> c'4 d' g' f' es'2 aes' dis'1
> }\layout {
> ragged-right = ##t
> \context { \Score
> \override BarLine #'space-alist #'next-note = #'(fixed-space . 1.8)
> }
> }}
In my opinion it looks even worse, because the unaccidentaled notes
get even more extra space.
2011/2/14 Neil Puttock <n.putt...@gmail.com>
>
> 2011/2/14 Janek Warchoł <lemniskata.bernoull...@gmail.com>:
>
> > The amount of whitespace after the barline is fixed, while it should depend
> > on whether the first note in the measure has an accidental or not. This
> > results in notes being too far from the barline, especially when there is
> > only one note in measure:
> >
> > { c'4 d' g' f' e'2 a' d'1 }
> > { c'4 d' g' f' es'2 a' dis'1 }
>
> Have you tried fiddling with BarLine #'space-alist? Changing the
> next-note entry to use minimum-fixed-space appears to deliver the
> goods:
>
> \override Staff.BarLine #'space-alist =
> #'((time-signature . (extra-space . 0.75))
> (custos . (minimum-space . 2.0))
> (clef . (minimum-space . 1.0))
> (key-signature . (extra-space . 1.0))
> (key-cancellation . (extra-space . 1.0))
> (first-note . (fixed-space . 1))
> (next-note . (minimum-fixed-space . 1.2))
> (right-edge . (extra-space . 0.0)))
Wow, looks like it does what i want! I didn't even know about
space-alists. Sorry for being ignorant...
As i'm not very familiar with this and therefore lack expertise, do
you imagine any possible side-effects?
If not, i think it would be good to change these values in default
LilyPond settings.
> This doesn't work for the single-note case since that's altered later
> using the grob property 'full-measure-extra-space (it overrides the
> space-alist default set by StaffSpacing).
That's a pity, especially because the single-note case is the worst
(in my opinion at least).
Looks like these two operations should be done in opposite order.
2011/2/15 Keith OHara <k-ohara5...@oco.net>:
> Mon, 14 Feb 2011 20:46:08 +0000 Neil Puttock:
>>
>> 2011/2/14 Janek WarchoÅ :
>>>
>>> The amount of whitespace after the barline is fixed, while it should
>>> depend
>>> on whether the first note in the measure has an accidental or not. This
>>> results in notes being too far from the barline, especially when there is
>>> only one note in measure:
>>>
>>
>> Have you tried fiddling with BarLine #'space-alist? Changing the
>> next-note entry to use minimum-fixed-space appears to deliver the
>> goods:
>
> If you want to let the accidental come closer to the barline, without
> increasing 'fixed-space to every note after a bar-line, and are willing to
> recompile, you can try the patch at http://codereview.appspot.com/4188051/
> (The patch removes code that changes the effect of #'space-alist for some
> notes.)
I'll try this.
Thanks!
Janek
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
