Thank you very much, Harm.
On Sat, Feb 21, 2015 at 10:52:52PM +0100, Thomas Morley wrote:
>
>
> harmonies = \new ChordNames
> \with {
> %% !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> %% from NR:
> %% "Setting staff-affinity to #f causes a non-staff line to be treated
> %% as a staff."
> %% Now 'ChordNames' are recognized by the spacing-engine and equal
> %% spacing should result, meaning the space between the upper Staff
> %% for melody and the ChordNames are always the same (not the space
> %% between two melody-Staffs, though.)
> %% More, 'VerticalAxisGroup.staff-staff-spacing' will work now, as a
> valid
> %% setting for score-spacing
> %% !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> \override VerticalAxisGroup.staff-affinity = ##f %% default is
> @code{DOWN}
> \override VerticalAxisGroup.staff-staff-spacing = #'(
> (basic-distance . 0.5)
> (minimum-distance . 0.5)
> (padding . 1)
> (stretchability . 0)
> )
> }
> \chordmode {
> \repeat unfold 9 { c2 a2:m | f2 g2 | s4 c s a:m | f2 g2 }
> }
I did not know that Lily does not by default recognize a
ChordNames context as a "staff" for the purposes of system
spacing! I always associated my problem with the RhythmicStaff,
because the wider-than-usual system spacing happened whenever
there was a non-hidden RhythmicStaff in a given system.
I can now make some aesthetic improvements to several of my
charts.
Thanks again!
Jim
_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user
