From: Bruce S. <Bru...@nc...> - 2004-05-13 00:11:10
|
That's odd. I ran lathe.py from the VPython demo suite and observed CPU=20 usage, which was less than 1% on a 2.6 GHz Windows XP machine. Note that=20 lathe.py makes a display and then ends. Even running stonehenge.py,=20 which has a continuous animation and looks for user mouse inputs, runs=20 at less that 1%. There is a rendering thread which many times per second=20 renders the scene, and it isn't "smart" -- it doesn't do any=20 optimization but every time clears some memory to black and repaints the=20 whole scene. But this is a fast process. Yes, you can nest frames within frames. Bruce Sherwood Kuzminski, Stefan R wrote: > My vpython app takes up 50% or so of the cpu just sitting there ( on a=20 > windows box ). I put a sleep in my top level loop, but it didn=92t see= m=20 > to help, maybe there is a thread eating up lots of cpu within vpython? >=20 > also, >=20 > Can I nest frames within frames? >=20 > thanks, >=20 > S |