On 2020-09-24 4:42 am, Dan Eble wrote:
On Sep 24, 2020, at 05:51, Jan-Peter Voigt <jp.vo...@gmx.de> 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 in this particular timestep. If this the intended
behaviour I appreciate it because it is consistent. The
"start-trans.."
slot wasn't called before for instant voices, but for regular
installed
contexts. So now I have to finish "initialize" of the engraver with
"start-trans..." in any case.
So my question is if this is intended and not likely to change?
Sorry, if I missed discussion about this!
This change was intended.
https://gitlab.com/lilypond/lilypond/-/merge_requests/292
specifically, commit fe9242659305dce587bd1fcdcc7b0ac62df25ad6
Does this not actually increase complexity? An engraver that only
needed to handle start-translation-timestep now needs to handle
initialize as well or else it misses the opportunity to set up state.
-- Aaron Hill
