On Wed, 13 Feb 2008, Brian Fisher wrote:
There is a way to get an app in windows to not be blocked by event
processing like that (something about calling your update from a
particular message or returning the right value from some weird barely
documented message or something like that) but I
Sorry I didn't express myself well - I didn't mean to say the time
elapsed didn't matter, I meant to say that one's movement was also
controlled by code, specifically the % like you pointed out:
if (frame_num%5)==0:
x2 = x2+distance_moved*5.
so in that way they are very different.
What I
Looking at the pyglet mailing list archives, it seems the way Alex
co. get the event loop to pump during window move and resize events is
to handle the WM_USER+7174 windows message - which told windows not to
do resize and move operations in a tight inner loop anymore.
On Feb 12, 2008 12:58 PM,
in windows, when people are clicking the title bar they are moving the
window (even if not moving the mouse). And by default, moving or
resizing blocks in your message loop (basically this line doesn't
return in the way you'd like: for event in pygame.event.get():)
since one sprite is moved by
