Fix use of global render/audio managers #14

Open
opened 2022-10-05 12:42:15 +01:00 by tlater · 0 comments
Owner

Currently, the music player and webgl renderers are implemented as global variables with a whole bunch of internal state.

They probably need to stay that way, but their interactions with react are unfortunate; specifically, react's useEffect is worked around a lot to get the visualizer to render, and at the same time some of redux' side-effect-freeness is violated in order to update the audio manager's source.

I need to find a better way of managing these.

Originally posted by @tlater in tlaternet/tlaternet-templates#7 (comment)

Currently, the music player and webgl renderers are implemented as global variables with a whole bunch of internal state. They probably need to stay that way, but their interactions with react are unfortunate; specifically, react's `useEffect` is worked around *a lot* to get the visualizer to render, and at the same time some of redux' side-effect-freeness is violated in order to update the audio manager's source. I need to find a better way of managing these. _Originally posted by @tlater in https://gitea.tlater.net/tlaternet/tlaternet-templates/issues/7#issue-86_
tlater added the
templates
label 2022-10-05 13:22:47 +01:00
Sign in to join this conversation.
No labels
server
templates
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tlaternet/tlaternet-webserver#14
No description provided.