Hey guys,
I'm looking at this example now and am not sure what to do with it. While
it's true that the tempoMark scheme function itself is not necessary now
that \tempo does the same thing, it's also true that the point of this
passage in the LM 5.1.5 is to show how use definitions and to place them in
separate \include files, not to teach "how to display a tempo marking."
Maybe I should come up with some other score marking that could be used
instead of a tempo marking, or do you think that whole macro can just be
deleted from the example and the "mpdolce" macro will suffice as an example
to stick in a definitions file?
Trevor, do you have thoughts on this? This example also occurs in NR 6.1.2,
Interfaces for programmers.
Jon
On Sun, May 10, 2009 at 8:55 AM, Graham Percival
<gra...@percival-music.ca>wrote:
> Where in the world is Carmen Sandi... oops, wrong example.
>
> If "the \tempoMark" exaple is in the NR, then Jonathan should
> figure out what you're talking about and prepare the patch.
>
> If "the \tempoMark" example is in the LM... then hey, this is
> simple enough, Jonathan should still prepare a patch. Unless it'd
> destroy the continuity of the LM or something, in which case he
> should consult with Trevor.
>
> Cheers,
> - Graham
>
>
> On Sun, May 10, 2009 at 08:05:06AM -0400, Kieren MacMillan wrote:
> > Hi,
> >
> > The \tempoMark example should be completely rewritten to use \tempo
> > (i.e., MetronomeMark) instead of overriding RehearsalMark -- e.g., the
> > first entry should read
> >
> > mpdolce = #(make-dynamic-script (markup #:hspace 1 #:translate (cons 5 0)
> > #:line(#:dynamic "mp" #:text #:italic "dolce" )))
> > \relative c'' {
> > \tempo 4=50
> > a4.\mpdolce d8 cis4--\glissando a | b4 bes a2
> > \tempo \markup { "Poco piu mosso" }
> > cis4.\< d8 e4 fis | g8(\! fis)-. e( d)-. cis2
> > }
> >
> > If you do this, all the issues you mention will go away... or, at least,
> > be transformed into different issues! ;)
> >
> > Unfortunately, I've got no time to do a patch now -- I've got a huge
> > commission due in a week *and* a new musical opening three days after
> > that [!!] -- but hopefully someone will pick up the ball and run with
> > it, so that this example doesn't continue to mislead readers.
> >
> > Cheers,
> > Kieren.
>
--
Jonathan Kulp
http://www.jonathankulp.com
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
