[Top][All Lists]

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

Re: (scheme-)engraver in 2.20/21

From: Jan-Peter Voigt
Subject: Re: (scheme-)engraver in 2.20/21
Date: Thu, 24 Sep 2020 17:09:22 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0

Am 24.09.20 um 16:28 schrieb Aaron Hill:
> I doubt this is the sort of thing convert-ly could patch, so the
> proposed change in behavior would break user-created engravers that
> expect to always get a pair of (start|stop)-translation-timestep calls. 
> As such, it makes far more sense that LilyPond automatically take care
> of invoking start-translation-timestep after initialize.
OK that sounds reasonable

> The argument for uniform behavior is sound, though one must be careful
> the behavior to which you are aligning is correct.  My vote is that
> "starts" and "stops" must always be paired.  If there were cases where
> "start" was not occurring, *that* is the faulty behavior to address.
I agree. For now I can live with the faulty but uniform behaviour, but a
change in that direction should be developed.

reply via email to

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