Hi Jon (et al),
Now there's also a "tempoMark" function defined in NR 6.1.2,
Interfaces for programmers. My instinct is to leave this one
alone--it is not obsolete, since the predefined \tempo command does
not take a $padding argument like this bit of scheme does, right?
IMO, we [in the docs] should *not* be encouraging the use of
RehearsalMarks for tempo indications -- this is exactly why the
\tempo command was rewritten [can't remember by whom at the moment,
but "thanks!"].
In other words, this example should *also* be changed... maybe
something like
tempoPadded = #(define-music-function (parser location padding
tempotext)
(number? string?)
#{
\once \override Score.MetronomeMark #'padding = $padding
\tempo \markup { \bold $tempotext }
#})
\relative c'' {
\tempo \markup { "Low tempo" }
c4 d e f g1
\tempoPadded #4.0 #"High tempo"
g4 f e d c1
}
This still demonstrates the use of a music function to provide
padding (e.g.), but uses the correct grob.
Yes?
Kieren.
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
