On Saturday, December 3, 2016 at 2:30:36 PM UTC-8, William wrote: > > On Sat, Dec 3, 2016 at 2:28 PM, Paul Masson <paulm...@comcast.net > <javascript:>> wrote: > > There's apparently no good way in general to test whether the scene is > > unchanged. This is a known issue: > > > > https://github.com/mrdoob/three.js/issues/7670 > > > > One of the comments on this thread offers another option: only render > the > > scene upon user interaction. I'm so accustomed to writing Three.js to be > > ready for animation that I didn't think about this. If we restrict > Three.js > > usage in Sage to static scenes then CPU usage drops to nothing. > > > > I'm happy to make this change, but this means no animations in the > scenes > > for now. > > What kind of animations are currently implemented? > I can only think of spin=[number]. > > -- William >
None right now, but the changes necessary to get rendering to work without an animation loop don't play nicely with requestAnimationFrame. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
