-
Notifications
You must be signed in to change notification settings - Fork 21
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
Shiny displays are too slow #4
Comments
Naive question, does that mean a scene cannot be controlled by reactive variables in a shiny app? I am new to rgl but I do like the concept of rendering scenes within a shiny app based on data within the app. |
No, it just makes it harder to do. It's easy to generate a new scene in Shiny, but that's slow. What you need to do is to figure out how to trigger some Javascript that will send messages to the existing scene. See the WebGL vignette for examples where the messages are generated by HTML controls like buttons and sliders. If your Shiny code can generate those messages, that will be quick. |
Are there examples available with multiple vertices being simultaneously updated by vertexControl()? I haven't been able to wrap my head around it, unfortunately. I would greatly appreciate being able to avoid redraws of an existing scene when plotting meshes in a Shiny app. |
Here's a simple one. It starts with a cube (which is rendered as 6 quads, with 24 total vertices), and then rotates two of the vertices around the z axis.
|
An rgl scene can be shown in a Shiny app, but small changes to the scene take a long time to show up, because currently the whole scene needs to be sent to the browser and processed; there isn't an easy way to say to update the current scene with minimal new data transferred.
The text was updated successfully, but these errors were encountered: