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
{{ message }}
This repository has been archived by the owner on Jan 17, 2020. It is now read-only.
Currently Helm works like Elm does - there's no way to kill rendering (AFAIK). There needs to be some sort of state sent back as well as the Element objects used for rendering (as well as something like Sound). This state would allow you to signify that the engine should be destroyed.
The text was updated successfully, but these errors were encountered:
It needs to be type-safe, though. We can't just use a Maybe Element or the equivalent; we have to force the user to never do anything after the engine is killed.
Note that this will be quite easy to implement in Helm 1.0. All that's needed is a new quit function that returns a Cmd that stops the engine at the next tick, which will then safely close up resources & is type safe.
Currently Helm works like Elm does - there's no way to kill rendering (AFAIK). There needs to be some sort of state sent back as well as the
Element
objects used for rendering (as well as something likeSound
). This state would allow you to signify that the engine should be destroyed.The text was updated successfully, but these errors were encountered: