Original Post
Hello, The question might be trivial, but there is an annoying thing about my application: when I move with the mouse any window or dialog belonging to my application, the windows message queue seems to be fully concentrated into that task (the application is stuck somewhere in the PeekMessage-TranslateMessage-DispatchMessage routine). Same happens when navigating the window's menus, during a window resizing action, etc. Can someone explain me why this is and if there is a way around this? (without using another thread) . My application is running a simulation that displays graphics that come to a halt in those situations. Or, is there a signal that I could track that will tell me: "We are going to enter such a situation now"?