WinMain loop pauses when the application window is grabbed by mouse and resized?
-
Hi all, I'm using C++ with Win32 API, no MFC. I have a game with a normal game loop in the WinMain function. Within the loop I call all the processing and drawing and such. But for some reason, when I grab the edge of the application window with my mouse and resize it, the game loop just pauses. I still seem to be receiving WM_SIZING and WM_PAINT messages, which doesn't make sense because my PeekMessage is in the game loop and is not being called. I don't understand what's going on. Anyone have any ideas? Thanks!! KR
-
Hi all, I'm using C++ with Win32 API, no MFC. I have a game with a normal game loop in the WinMain function. Within the loop I call all the processing and drawing and such. But for some reason, when I grab the edge of the application window with my mouse and resize it, the game loop just pauses. I still seem to be receiving WM_SIZING and WM_PAINT messages, which doesn't make sense because my PeekMessage is in the game loop and is not being called. I don't understand what's going on. Anyone have any ideas? Thanks!! KR
Can you post the snippet of the loop? I have the suspect you are using the Win32 message dispatching improperly
2 bugs found. > recompile ... 65534 bugs found. :doh:
-
Hi all, I'm using C++ with Win32 API, no MFC. I have a game with a normal game loop in the WinMain function. Within the loop I call all the processing and drawing and such. But for some reason, when I grab the edge of the application window with my mouse and resize it, the game loop just pauses. I still seem to be receiving WM_SIZING and WM_PAINT messages, which doesn't make sense because my PeekMessage is in the game loop and is not being called. I don't understand what's going on. Anyone have any ideas? Thanks!! KR
I might be wrong but as far as i know when you grab the window or size it, an "internal message loop" starts (probably it's somewhere inside one of the system DLLs, just a guess too) that handles the move/size operation, filters out some messages and lets others reach your window(s).
> The problem with computers is that they do what you tell them to do and not what you want them to do. < > "It doesn't work, fix it" does not qualify as a bug report. < > Amazing what new features none of the programmers working on the project ever heard of you can learn about when reading what the marketing guys wrote about it. <