lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: \crescTextCresc... 2.10 vs 2.12


From: Reinhold Kainhofer
Subject: Re: \crescTextCresc... 2.10 vs 2.12
Date: Sat, 31 Jan 2009 18:54:56 +0100
User-agent: KMail/1.11.0 (Linux/2.6.27-9-generic; KDE/4.2.0; i686; ; )

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Samstag, 31. Januar 2009 18:09:46 Graham Percival wrote:
> On Sat, Jan 31, 2009 at 04:58:16PM +0100, Frédéric Bron wrote:
> > I upgraded to 2.12 and dicovered that \crescTextCresc is not set for
> > ever instead of just for the next crescendo.
>
> Sounds like a bug.  In fact, I was fairly certain that it's
> already in the issue tracker, although I couldn't find it in 60
> seconds of searching.

Actually, it's the other way round: \setTextCresc was documented (and meant) 
to apply only to the next crescendo, although in reality it was never reset 
and its effect continued for all following crescendi. This behavior was fixed 
in 2.12 and the effect now really only applies to the next crescendo as 
documented.

However, you can easily replace \crescTextCresc by your own function, which 
uses \override instead of \once \override, to change the crescendo type once 
and for all.

IIRC, we also had a discussion a while ago to make \< create a hairpin and 
\cresc to create a text crescendo, which makes much more sense, as the 
pictorial commands already incidate the outcome. I don't know the result of 
that discussion, though.

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQFJhJByTqjEwhXvPN0RAlFrAJ9FoYcJv55nJWphZYwj9xsMtS2gcgCgs285
KKi+1jSSWqhDgfJv+4/khGA=
=bvS2
-----END PGP SIGNATURE-----




reply via email to

[Prev in Thread] Current Thread [Next in Thread]