On Nov 13, 2007 6:43 PM, Alex Holkner <[EMAIL PROTECTED]> wrote: > > It's windows. Dragging a window always locks up your main thread on > > windows. go ahead and try it with a non-python game that has an > > animated main menu and a windowed mode. You'll see. > > This has bugged me in the past. How do IE, WMP, Firefox, etc. all > manage to keep their animations running while the window is being > resized? Do they all use a separate rendering thread? > Either another thread or they use the WM_MOVING & the WM_RESIZING to do work in. Windows does this weird thing where it makes your main thread be in this tight loop of calling your message handler for the thing that's going on, but it doesn't return from the dispatchMessage call or whatever. I have no idea why it does that.
-- One other weird side effect of this thing is that it used to mean that apps couldn't be moved or resized unless they were processing their message loop. It used to mean that hung/busy apps couldn't be moved or minimized. I think they added something starting in winXP where if the app doesn't respond soon enough (like a half a second or something), XP suspends the app thread and does the move/resize/minimize work itself. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
