Re: vertical spacing scrambles systems

[Eluze]

Keith OHara wrote
> Eluze 
> <eluzew <at>
>  gmail.com> writes:
> 
>> 
>> maybe the same bug!?
>> 
>> \paper {
>>   system-system-spacing = #'((stretchability . 666))
>>   score-system-spacing = #'((stretchability . 666))
>> }
>>   \new Staff { f1 \break g1 }
>>   \new Staff { f1 \break g1 }
>> 
> 
> That's not a bug; that's parody of a horrible user interface.
> 
> 'system-system-spacing is usually a list of pairs defining
> 'basic-distance, 'minimum-distance, 'padding, and 'stretchability.
> 
> Using a list with one element, he defines stretchability only, 
> making 'basic-distance and 'padding undefined.  The undefined 
> parameters are taken as zero, which would be reasonable if not for
> the mysterious way these parameters lost their default values.
> 
> On the slim chance that this was an honest misunderstanding, the way to
> set
> 'stretchability, while leaving the others at their non-zero default
> values, is
>   system-system-spacing #'stretchability = 666

thanks for these clarifying words!

when I (re-)read the passage about modifying alists in NR (chapter 5.3.6)
I'm getting a bit confused: there is an example how to set all values to
zero and it lists every available parameter and sets it to zero:

\new PianoStaff \with {
\override StaffGrouper.staff-staff-spacing =
  #'((basic-distance . 0)
  (minimum-distance . 0)
  (padding . 0)
  (stretchability . 0))
}

but it would be much easier (and sufficient) to write

\override StaffGrouper.staff-staff-spacing = #'((basic-distance . 0))

or even

\override StaffGrouper.staff-staff-spacing = #'()

please correct me if I'm wrong!


tbh - I was only half-aware of the fact that alists are always completely
overridden when one is not using nested overrides - partly probably because
the doc speaks of /default-when-unset/ values (where are these values set?)
or /files being loaded each time an input file is compiled/ (is this
important here?). it's difficult to understand the meaning or difference of
standard and default-when-unset settings when they are not all explained.

so finally I'd like to raise the question: is the user interface so horrible
or is it the (partial) lack of adequate documentation?

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/vertical-spacing-scrambles-systems-tp136247p136391.html
Sent from the Bugs mailing list archive at Nabble.com.