|
From: | Mats Bengtsson |
Subject: | Re: Renaming \setTextCresc, \setHairpinCresc, etc. |
Date: | Wed, 30 Apr 2008 10:17:54 +0200 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20061113 Debian/1.7.8-1sarge8 |
Note that these settings don't behave like most others. As is illustrated in the following example, the property setting is only used for the first following dynamic indication and is then automatically reset again. With the current semantics, this means that it doesn't make sense to have \xxxOn and \xxxOff macros. I'm not sure if this is the intended and desired behaviour, so perhaps it's better to first change the implementation and then the naming. \relative{ c\< d e f\! \setTextCresc c\< d e f\! c\< d e f\! } /Mats Valentin Villenave wrote:
2008/4/30 Graham Percival <address@hidden>:We could even go with pairs of: \crescText \crescHairpinPatrick's idea was better IMO, as it introduced textual crescendo indications as an "exception" to default (hairpin) crescendos. Therefore, using \crescTextOn and Off avoided to ever use Hairpin (I may be influenced as a non-English speaker here: as much as the word "text" looks familiar to me, the word "hairpin" hardly makes any sense, and I suspect it's a bit more difficult to use for every foreign LilyPonders out there...). Cheers, Valentin _______________________________________________ lilypond-devel mailing list address@hidden http://lists.gnu.org/mailman/listinfo/lilypond-devel
-- ============================================= Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: address@hidden WWW: http://www.s3.kth.se/~mabe =============================================
[Prev in Thread] | Current Thread | [Next in Thread] |