What's happening is that for simplicity and robustness VPython renders
the scene about 25 frames per second, each time starting from a blank
slate. No attempt is made to determine whether any change has been made
to the scene. Obviously in principle the architecture could be changed
to make it unnecessary to do more than check for interactions, but
that's not the current architecture.
Bruce Sherwood
On 4/10/2010 3:15 PM, Lenore Horner wrote:
> If I run a python program that uses vpython to make a scene and then
> leave the scene sitting open (no looping going on), I find that python
> ends up consuming 30-50% of my CPU cycles. Is this normal? If
> something were happening, I wouldn't be so surprised, but all that
> should be happening is the default checks to see if I interacted with
> the window in any way (rotating or zooming).
>
> Lenore Horner
>
>
>
|
