New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
useRenderLoop().onLoop
ticks before the renderer can meaningfully render
#595
Labels
Comments
andretchen0
added
the
p2-to-be-discussed
Enhancement under consideration (priority)
label
Mar 30, 2024
Hey @alvarosabu ! I saw that you labelled this as For now, I'm trying to submit issues highlighting rough spots encountered while building things with Tres. My hope is that in assembling the issues, we'll be able to knock all (or most) of them out at once. |
andretchen0
added
p3-minor-bug
An edge case that only affects very specific usage (priority)
and removed
p2-to-be-discussed
Enhancement under consideration (priority)
labels
Apr 4, 2024
This was referenced Apr 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Problem
useRenderLoop().onLoop
ticks before the renderer can meaningfully render.When
onLoop
is initially called, e.g.:These values change on the subsequent frame, making coding/debugging more difficult than necessary.
Solution
useRenderLoop()
should be dependent on thecontext
's renderer.onLoop
until the renderer is ready.Context
pause
immediately afteronLoop
doesn't do anything #251useRenderLoop
per page share state #252Reproduction
https://stackblitz.com/edit/tresjs-basic-t6zfd2?file=src%2Fcomponents%2FUseRenderer.vue
Steps to reproduce
See StackBlitz.
System Info
Used Package Manager
npm
Code of Conduct
The text was updated successfully, but these errors were encountered: