Re: graphic memory & animation

2005-10-17 Thread Mike C. Fletcher
Peres wrote: > Thanks a lot for your answer, Fredrik, > Slow means more than 20ms to erase the screen. After double buffering > it improved a lot , of course (16 ms) but I'll need a faster speed. > I program 2D animated sequences on a PC. Do you think OpenGL is the > correct direction to take? I

Re: graphic memory & animation

2005-10-17 Thread Fredrik Lundh
"Peres" wrote: > Slow means more than 20ms to erase the screen. After double buffering it > improved a lot , of course (16 ms) but I'll need a faster speed. are you measuring the time it takes to go from a populated screen to a blank screen? if so, you're probably seeing the screen refresh time

graphic memory & animation

2005-10-17 Thread Peres
Thanks a lot for your answer, Fredrik, Slow means more than 20ms to erase the screen. After double buffering it improved a lot , of course (16 ms) but I'll need a faster speed. I program 2D animated sequences on a PC. Do you think OpenGL is the correct direction to take? If so is it easy to i

Re: graphic memory & animation

2005-10-13 Thread Fredrik Lundh
"Peres" wrote: > Python is great!... but the erasing of the graphic memory is slow (I used > surf.fill from Pygame). define slow. > Does anyone know how to erase the screen faster, in animated graphics? if you're doing animation on modern hardware, there's hardly any reason not to use double bu

graphic memory & animation

2005-10-13 Thread Peres
Hello! Python is great!... but the erasing of the graphic memory is slow (I used surf.fill from Pygame). Does anyone know how to erase the screen faster, in animated graphics?   With many thanks   Valerie Peres   -- http://mail.python.org/mailman/listinfo/python-list