Right now there is a pause/play button for visualizers, but various occurrences such as a resize alter the state of that. As it is a human-manipulated control, we want to give it more respect. So we want to create a stronger "Paused State": clicking the pause button puts a visualizer in Paused State, and nothing can leave that state short of another specific human interaction, e.g., clicking the play button (and maybe only that gesture).
While in the Paused State, a visualizer is allowed to draw at most one new frame as a consequence of any other interaction: resizing, parameter update, mouse click, etc. It should not have mouseover behaviors while paused (unless anyone disagrees with that restriction). See https://github.com/orgs/numberscope/discussions/6#discussioncomment-10006613
Right now there is a pause/play button for visualizers, but various occurrences such as a resize alter the state of that. As it is a human-manipulated control, we want to give it more respect. So we want to create a stronger "Paused State": clicking the pause button puts a visualizer in Paused State, and nothing can leave that state short of another specific human interaction, e.g., clicking the play button (and maybe only that gesture).
While in the Paused State, a visualizer is allowed to draw at most one new frame as a consequence of any other interaction: resizing, parameter update, mouse click, etc. It should not have mouseover behaviors while paused (unless anyone disagrees with that restriction). See https://github.com/orgs/numberscope/discussions/6#discussioncomment-10006613