Re: Can't set next-padding - it's ignoring me

[Anthony W. Youngman]

In message <address@hidden>, Nicolas Sceaux 
<address@hidden> writes
> "Anthony W. Youngman" <address@hidden> writes:
>
> > Actually, looking at 11.3.4, is it possible that it could be
> > \overrideProperty, not \outputProperty?
>
> Right.
> \overrideProperty is a music function, and thus cannot be used in
> \layout or \paper blocks. Use it in your music.

But the example (and what I used) says *OUTPUT*Property. Which lilypond 
has objected to as "unrecognised" wherever I tried to use it!

So one of my questions (which you have ignored...) was "is *output* a 
mistake?". In which case, there's a bug somewhere, because the 
documentation and the program are out of sync.

The point is, if I follow the instructions in the manual to try and 
change next-padding, lily won't compile my .ly file and blows up with an 
error.
> > > http://lilypond.org/doc/v2.9/Documentation/user/lilypond/Vertical-spacin
> > > g-between-systems.html
> > >
> > > The paper property to tune are between-system-padding and
> > > between-system-space.
> >
> > I haven't got the output in front of me, but with "annotate-spacing =
> > ##t" it tells me that next-padding is 2.8, and I wanted to change it
> > ...
>
> There's something not quite intuitive about padding and space lengths. It
> seems that both are not expressed in the same unit, so when you specify
> padding=5 it actually shows 2.8. Space lengths show as expected.
>
> > > \paper {
> > >  between-system-padding = 5
> > >  between-system-space = 0.1
> > >  annotate-spacing = ##t
> > >  ragged-bottom=##t
> > > }
> >
> > I'll try that, but I've probably done that already (as I say, I don't
> > have it in front of me :-( I'll let you know what happens, but I've
> > probably already set both of those to 0 ... if I haven't, it's because
> > of the following ...
>
> Please try the example before saying that it does not work. And play
> with it by using different values, to figure out how the spacing of
> systems works it ragged condition.

I didn't say it doesn't work! I said "I think I've already done that, 
and it behaved as expected"!

And I MAY try it, as soon as I get back to the computer with my work on. 
I said *MAY* because I don't see how I can *try* to do something that 
I'm already doing ...
> BTW, setting space to 0 may not be a good idea, as I seem to recall that
> space is used as a denominator somewhere in the spacing algo.
>
> > NB - whoever coded annotate-spacing - is it possible to code it so the
> > information doesn't clash? Most of it is illegible because it one bit
> > of information opaquely overprints another bit with the result that
> > maybe 80% is whited out :-(
>
> This is possible, but as with all bug reports, an example showing the
> problem is somewhat required to fix it. And you didn't mention what
> version you're using. (The look of annotations changed during 2.9)

Ah. I'm running 2.8.4. I can email you a pdf on monday if you like.
> nicolas

Cheers,
Wol
--
Anthony W. Youngman - wol at thewolery dot demon dot co dot uk
HEX wondered how much he should tell the Wizards. He felt it would not be a
good idea to burden them with too much input. Hex always thought of his reports
as Lies-to-People.
The Science of Discworld : (c) Terry Pratchett 1999