[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Measure width adaptation to tempo indications centered above MMR
From: |
Neil Puttock |
Subject: |
Re: Measure width adaptation to tempo indications centered above MMR |
Date: |
Sat, 17 Sep 2011 23:43:22 +0100 |
On 17 September 2011 23:30, Xavier Scheuer <address@hidden> wrote:
> However I do not find a clean way with LilyPond to have the measure
> width to adapt to the text length. Would you recommend me to use
> MetronomeMark, MultiMeasureRestText or TextScript?
MultiMeasureRestText. If you set springs-and-rods, it will stretch
the bar to accommodate (and still be centred on the rest).
\override MultiMeasureRestText #'springs-and-rods =
#ly:multi-measure-rest::set-text-rods
> On the LSR one can find snippet #659 : "Forcing measure width to adapt
> to MetronomeMark's width". http://lsr.dsi.unimi.it/LSR/Item?id=659
> The idea is more elegant but the result is not centered with 2.15.11.
> Why? And would it be possible to have it centered?
Because tempo marks over full-bar rests are now anchored on the left
barline instead of the PaperColumn to the left of the rest.
> And finally, why can't we use something simple based on
> MultiMeasureRestText? For instance:
> \override MultiMeasureRestText #'extra-spacing-width = #'(0 . 0)
> (which does not seem to work, it does not affect the spacing !!
> and the text is not *centered* above the multi-measure rest).
See the internals reference. extra-spacing-width is part of
item-interface, which means it only works with Item objects (i.e,
grobs with fixed width/height like font-glyphs). A
MultiMeasureRestText object is a Spanner (it has to be, since it's the
child of another spanner, the MultiMeasureRest), so responds to
minimum-length and springs-and-rods.
Cheers,
Neil