You where right anonytmouse. :) I set ofn.hwndOwner to null to seperate it from my main window, and the problem is no more.
Thanks for the help. :)
So what would I have to do to prevent that, while keeping my hwnd the parent?
Printable View
You where right anonytmouse. :) I set ofn.hwndOwner to null to seperate it from my main window, and the problem is no more.
Thanks for the help. :)
So what would I have to do to prevent that, while keeping my hwnd the parent?
Changing
toCode:case WM_PAINT:
{
BeginPaint(hwnd, &ps);
BitBlt(ps.hdc, 0, 0, nWndWide, nWndHigh, hdcBuffer, 0, 0, SRCCOPY);
EndPaint(hwnd, &ps);
break;
}
works like I guessed, but is this a bad idea to do?Code:case WM_PAINT:
{
BeginPaint(hwnd, &ps);
BitBlt(ps.hdc, 0, 0, nWndWide, nWndHigh, hdcBuffer, 0, 0, SRCCOPY);
EndPaint(hwnd, &ps);
return 0;
}
From MSDN:With "break" you are returning whatever value is in the return statement at the end of your window proc, whereas with "return 0" you are explicitly returning 0 right then and there. Since WM_PAINT says to do this, I'd go with the second one, but really, I believe your window proc should be returning 0 anyways, so if its not, thats another problem you might want to look into.Quote:
Originally Posted by MSDN