On Fri, May 30, 2008 at 1:39 PM, Graham Percival <[EMAIL PROTECTED]> wrote:
>
> Hmm... I actually preferred your original names. Although I *do*
> like the \dimAs{Decresc/decr/dim}, since it links back to the \<
> \> concept (ie decresc/decr/dim are all interally the same).
Yes, I like how Trevor
On Fri, 30 May 2008 12:38:43 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Fri, May 30, 2008 at 12:27 PM, Trevor Daniels
> <[EMAIL PROTECTED]> wrote:
> >
> > I think is this too complicated. For crescendos there are just
> > two possibilities - cresc. or hairpins - and for decrescendos
On Fri, May 30, 2008 at 12:27 PM, Trevor Daniels <[EMAIL PROTECTED]> wrote:
>
> I think is this too complicated. For crescendos there are just
> two possibilities - cresc. or hairpins - and for decrescendos
> there are four - decresc., decr., dim or hairpin. That is, six
> altogether, so why do w
- Original Message -
From: "Patrick McCarty" <[EMAIL PROTECTED]>
To: "Valentin Villenave" <[EMAIL PROTECTED]>
Cc:
Sent: Friday, May 30, 2008 7:47 PM
Subject: Re: Renaming \setTextCresc, \setHairpinCresc, etc.
On Fri, May 30, 2008 at 6:12 AM, Vale
On Fri, May 30, 2008 at 6:12 AM, Valentin Villenave
<[EMAIL PROTECTED]> wrote:
> 2008/4/30 Graham Percival <[EMAIL PROTECTED]>:
>> On Tue, 29 Apr 2008 22:43:59 -0700
>> Patrick McCarty <[EMAIL PROTECTED]> wrote:
>>
>>> I would like to propose that we rename the textual crescendo and
>>> decrescendo
2008/4/30 Graham Percival <[EMAIL PROTECTED]>:
> On Tue, 29 Apr 2008 22:43:59 -0700
> Patrick McCarty <[EMAIL PROTECTED]> wrote:
>
>> I would like to propose that we rename the textual crescendo and
>> decrescendo commands to names that are more intuitive and are more
>> internally consistent. The
2008/5/2 Reinhold Kainhofer <[EMAIL PROTECTED]>:
> Okay, so now that it is not reset any more: Is there an EASY way to generate
> just one text crescendo? I have always wondered why the crescendo type was
> using a global variable, which does not allow you to override it for one
> time.
>
>
I have just committed a rewrite of the dynamics engravers that does
away with this feature. I haven't yet thought of a proper convert-ly
rule though.
2008/4/30 Werner LEMBERG <[EMAIL PROTECTED]>:
> > Note that these settings don't behave like most others. As is
> > illustrated in the following
On Thu, 1 May 2008 23:13:26 +0100
"Trevor Daniels" <[EMAIL PROTECTED]> wrote:
> Graham Percival wrote
>
> >> In the meantime, the current behavior of \setTextCresc and the
> >> others
> >> -- that they are only applied once -- should be documented. Would
> >> this be more appropriate in the main
Graham Percival wrote
In the meantime, the current behavior of \setTextCresc and the others
-- that they are only applied once -- should be documented. Would
this be more appropriate in the main body of NR 1.3.1.2 or in
@knownissues?
@knownissues.
Is this a change in policy? Previously an
On Thu, 1 May 2008 13:33:03 -0700
"Patrick McCarty" <[EMAIL PROTECTED]> wrote:
> On Wed, Apr 30, 2008 at 12:42 AM, Graham Percival <[EMAIL PROTECTED]>
> wrote:
> > We could even go with pairs of:
> > \crescText
> > \crescHairpin
>
> I still think we should scrap the Hairpin commands.
Don't
On Wed, Apr 30, 2008 at 12:42 AM, Graham Percival <[EMAIL PROTECTED]> wrote:
>
> I prefer on/off. However, I'm not certain whether we want to go
> with
> \textCrescOn
> or
> \hairpinCrescOn
> (with Off being the opposite, of course)
>
> We could even go with pairs of:
> \crescText
> \
> 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.
This is a bug IMHO which I've reported a long time ago...
Werner
Cc:
Sent: Wednesday, April 30, 2008 9:17 AM
Subject: Re: Renaming \setTextCresc, \setHairpinCresc, etc.
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 t
2008/4/30 Mats Bengtsson <[EMAIL PROTECTED]>:
> 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.
I wasn't aware of that; l
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 a
2008/4/30 Graham Percival <[EMAIL PROTECTED]>:
> We could even go with pairs of:
> \crescText
> \crescHairpin
Patrick'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 eve
On Tue, 29 Apr 2008 22:43:59 -0700
Patrick McCarty <[EMAIL PROTECTED]> wrote:
> I would like to propose that we rename the textual crescendo and
> decrescendo commands to names that are more intuitive and are more
> internally consistent. The current implementation uses the "hairpin"
> commands t
2008/4/30 Patrick McCarty <[EMAIL PROTECTED]>:
> Since hairpins are the default output -- using \< and \> -- shouldn't
> the revert commands indicate that the "textual" (de)crescendo marks
> are being turned off? Maybe we should keep the \set... commands that
> set the alternative behavior (t
Hi List,
I would like to propose that we rename the textual crescendo and
decrescendo commands to names that are more intuitive and are more
internally consistent. The current implementation uses the "hairpin"
commands to revert the "text" commands, but I do not think this
solution is very intuit
20 matches
Mail list logo
