On Sep 24, 2020, at 10:28, Aaron Hill wrote:
>
> 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
On Sep 24, 2020, at 07:52, Aaron Hill wrote:
>
> On 2020-09-24 4:42 am, Dan Eble wrote:
...
>> This change was intended.
>> https://gitlab.com/lilypond/lilypond/-/merge_requests/292
>> specifically, commit fe9242659305dce587bd1fcdcc7b0ac62df25ad6
>
> Does this not actually increase complexity?
Jan-Peter Voigt writes:
> Hi all,
>
> after some other very involving projects I can now refocus on lilypond :-)
>
> I probably missed a change in 2.20/21. If I create a scheme-engraver the
> "start-translation-timestep" slot is not called, if the "initialize"
> slot has been called in this parti
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 LilyPo
On 2020-09-24 5:15 am, Jan-Peter Voigt wrote:
Hi Dan,
Am 24.09.20 um 13:42 schrieb Dan Eble:
On Sep 24, 2020, at 05:51, Jan-Peter Voigt wrote:
Hi all,
after some other very involving projects I can now refocus on
lilypond :-)
I probably missed a change in 2.20/21. If I create a scheme-en
Hi all,
I now have a use case for ly:version? documented in
http://lilypond.org/doc/v2.21/Documentation/usage/writing-code-to-support-multiple-versions
But the function is module-private in lily. The example on that page
does not compile and so doesn't any external file.
I can work around it wit
Hi Dan,
Am 24.09.20 um 13:42 schrieb Dan Eble:
> On Sep 24, 2020, at 05:51, Jan-Peter Voigt wrote:
>>
>> Hi all,
>>
>> after some other very involving projects I can now refocus on lilypond :-)
>>
>> I probably missed a change in 2.20/21. If I create a scheme-engraver the
>> "start-translation-ti
Am 24.09.20 um 13:40 schrieb Aaron Hill:
> On 2020-09-24 2:51 am, Jan-Peter Voigt wrote:
>> Hi all,
>>
>> after some other very involving projects I can now refocus on lilypond
>> :-)
>>
>> I probably missed a change in 2.20/21. If I create a scheme-engraver the
>> "start-translation-timestep" slot
On 2020-09-24 4:42 am, Dan Eble wrote:
On Sep 24, 2020, at 05:51, Jan-Peter Voigt wrote:
Hi all,
after some other very involving projects I can now refocus on lilypond
:-)
I probably missed a change in 2.20/21. If I create a scheme-engraver
the
"start-translation-timestep" slot is not ca
On Sep 24, 2020, at 05:51, Jan-Peter Voigt wrote:
>
> Hi all,
>
> after some other very involving projects I can now refocus on lilypond :-)
>
> I probably missed a change in 2.20/21. If I create a scheme-engraver the
> "start-translation-timestep" slot is not called, if the "initialize"
> slot
On 2020-09-24 2:51 am, Jan-Peter Voigt wrote:
Hi all,
after some other very involving projects I can now refocus on lilypond
:-)
I probably missed a change in 2.20/21. If I create a scheme-engraver
the
"start-translation-timestep" slot is not called, if the "initialize"
slot has been called
Hi all,
after some other very involving projects I can now refocus on lilypond :-)
I probably missed a change in 2.20/21. If I create a scheme-engraver the
"start-translation-timestep" slot is not called, if the "initialize"
slot has been called in this particular timestep. If this the intended
b
12 matches
Mail list logo
