>
>
>
> > 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?
> >
>
> \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
Thanks, Eluze. This has been added as issue 3482 :
https://code.google.com/p/lilypond/issues/detail?id=3482
Developers or other Bug Listers : would this have been more appropriately
labeled as :
*Type-Sc*ripts = Problem or desired feature in the non-build-system scripts
?
Ralph
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
