David Kastrup wrote
> Eluze <
> eluzew@
> > writes:
>
>> why do we have to specify a list for the
>> VerticalAxisGroup.staff-staff-spacing while e.g. for the
>> StaffGrouper.staff-staff-spacing you can define single items and also all
>> the other vertical spacers like default-staff-staff-spacing,
>> nonstaff-relatedstaff-spacing, nonstaff-unrelatedstaff-spacing etc.
>> accept
>> single values?
>
> Have an example?
here:
\score {
\new PianoStaff \with {
\override VerticalAxisGroup.staff-staff-spacing.basic-distance = #35
}
<<
\new Staff { c''1 c'' c''2 c'' }
\new Staff { \clef bass e1 f e2 d }
>>
}
and here is part of the log:
GNU LilyPond 2.17.23
…
warning: type check for `staff-staff-spacing' failed; value
`((basic-distance . 35) . #<unpure-pure-container #<primitive-procedure
ly:axis-group-interface::calc
:
:
taff-staff-spacing> #<primitive-procedure
ly:axis-group-interface::calc-pure-staff-staff-spacing> >)' must be of type
`list'
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/inconsistent-treatment-of-vertical-spacing-variables-tp148551p148559.html
Sent from the Bugs mailing list archive at Nabble.com.
_______________________________________________
bug-lilypond mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-lilypond
