   WM_SIZE ? [ solved ]
  Ok, so heres the problem. When I resize my window(finish resizing), I want to resize the backbuffer. Using WM_SIZE works great for this. However, Windows sends this message every time it realizes a window's size has changed, not just when you get done dragging it. In other words, you might be reseting your device a thousand times while you're resizing your window. I'm looking for a way around this. I want to be able to resize my backbuffer when I am DONE resizing my window. Anyone know how I can do this?[Edited by - Christopher Harris on June 19, 2006 12:50:41 PM]
  I just looked at my PSDK documentation, the WM_SIZE message "is sent to a window after its size has changed." It's the WM_SIZING that "is sent to a window that the user is resizing."...Anyway, if thats not working - dig into the DXUT sample framework. It can be a bit intimidating, but it contains the text-book methods for handling windows events/messages. Check to see what it does for a WM_SIZE event [smile]hthJack   ;  Thanks, Jack. I'll definitely look into the DXUT.I would like to mention though, that the only differance between the WM_SIZE and WM_SIZING messages are the information they send, not when they are sent. WM_SIZE sends you the new size of the window, and WM_SIZING sends you the side of the window that is being dragged. Both messages are sent every time there is a change in the size of the window.   ;  I just checked it out... you need to watch for WM_ENTERSIZEMOVE for the beginning of a resize event, WM_SIZE (or WM_SIZING) whilst its occuring and then WM_EXITSIZEMOVE when its complete. The enter/exit messages are one-time only.dxut.cpp -> DXUTStaticWndProc() for reference [smile]hthJack   ;  Wow, thanks alot! I find it funny that we may have been looking at the exact same code at the exact same time... :D Anyways thanks a lot for the help, I also found the WM_EXITSIZEMOVE message. This will hopefully keep my apps from crashing when I resize the window :)   