You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on a discussion in the Discord, it seems to me like there's value in being able to schedule callbacks that run synchronously with the clock. In particular, it strikes me as a little weird that StreamReplace and Transition are synced to the clock while all the other functions that modify the PlayMap are not, leading to unintuitive results like this:
do
d1 $ s "bd sn"
mute 1-- Won't have an effect if d1 hasn't been previously called
This moves all of the PlayMap code into the Stream module (which also might mean that StreamTypes.hs isn't necessary any more), and generally opens up a hook for implementing custom stream/clock extensions.
I can submit a PR along these lines, but I wanted to know what you all (though mostly @Zalastax) think.
The text was updated successfully, but these errors were encountered:
I like it a lot! But do we perhaps want two different action types? One for triggering the callback once (on a specific time) and another for triggering the callback repeatedly? And do we want the ability to de-register the callback? From inside or outside the callback? Both?
Following up on a discussion in the Discord, it seems to me like there's value in being able to schedule callbacks that run synchronously with the clock. In particular, it strikes me as a little weird that
StreamReplace
andTransition
are synced to the clock while all the other functions that modify thePlayMap
are not, leading to unintuitive results like this:I'd propose something like the following:
This moves all of the
PlayMap
code into the Stream module (which also might mean thatStreamTypes.hs
isn't necessary any more), and generally opens up a hook for implementing custom stream/clock extensions.I can submit a PR along these lines, but I wanted to know what you all (though mostly @Zalastax) think.
The text was updated successfully, but these errors were encountered: