Is there any way to change the background color of a messagebox?

[LarryChen]

Here is what I did,

oldHook = ::SetWindowsHookEx(WH_CALLWNDPROCRET, CallWndRetProc, NULL, ::GetCurrentThreadId());

MessageBox(...);

UnhookWindowsHookEx(oldHook);

Then within the callback function CallWndRetProc, I tried to change the background color of the dialog,

PAINTSTRUCT ps;
HDC hdc = BeginPaint(msg->hwnd, &ps);

::SetBkColor(hdc, RGB(255, 0, 0));

EndPaint(msg->hwnd, &ps);

But it doesn't change the background color of the dialog. I wonder what is the right way to do that? Thanks.

[Arjay]

Is this your process or are you hooking into another process?

[2kaud]

Does the SetWindowsHookEx() function succeed or fail as I don't see any code to check the returned value.

[LarryChen]

Is this your process or are you hooking into another process?

The call to SetWindowHookEx and the call to the callback function CallWndRetProc are in the same process.

[LarryChen]

Does the SetWindowsHookEx() function succeed or fail as I don't see any code to check the returned value.

Yes, it succeeds. Actually I can make use of the callback function CallWndRetProc to change the position of the dialog but I can't change the color of the dialog within the same callback function CallWndRetProc.

[Arjay]

See SetBkColor function

From the docs you'll see a link to Using Menus which shows SetBkColor done in OnDrawItem. Not sure if that helps you.

[2kaud]

For what message are you testing in your CallWndRetProc() when you execute a BeginPaint()/EndPaint() sequence?

As a message box is a dialog box, have you tried hooking the WM_CTLCOLORDLG message? See http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

[2kaud]

Also see WM_CTLCOLORMSGBOX http://winapi.freetechsecrets.com/wi...OLORMSGBOX.htm

[OReubens]

BeginPaint/EndPaint should ONLY be called in the handler for WM_PAINT using them at any other time can have weird results and sideeffects.

WM_CTLCOLORDLG is for controls on a dialog,
you probably want the WM_ERASEBKGND
though you will probably ALSO need to do some work in WM_CTLCOLORDLG to have the controls on the dialog patch with the dialog.

what you're asking for is highly "abnormal" and things will behave differently on different flavours of windows. You'll probably have an easier time to simply not use MessageBox() at all, but rather, create your own dialog with a custom background that displays the desired message.

The above may or may not work in combination with windows themes which have a different way of doing things, and your color changes may not fit into the theme at all. It may also have an assortment of issues when used with remote desktop.

[LarryChen]

BeginPaint/EndPaint should ONLY be called in the handler for WM_PAINT using them at any other time can have weird results and sideeffects.

WM_CTLCOLORDLG is for controls on a dialog,
you probably want the WM_ERASEBKGND
though you will probably ALSO need to do some work in WM_CTLCOLORDLG to have the controls on the dialog patch with the dialog.

what you're asking for is highly "abnormal" and things will behave differently on different flavours of windows. You'll probably have an easier time to simply not use MessageBox() at all, but rather, create your own dialog with a custom background that displays the desired message.

The above may or may not work in combination with windows themes which have a different way of doing things, and your color changes may not fit into the theme at all. It may also have an assortment of issues when used with remote desktop.

Now I created my own custom window and then within window procedure I tried to process the window message WM_ERASEBKGND, here is the code,

LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
	HDC hdc;

	switch (uMsg)
	{
	case WM_DESTROY:
		PostQuitMessage(0);
		return 0;
	case WM_ERASEBKGND:		
		PAINTSTRUCT ps;
		hdc = BeginPaint(hwnd, &ps);

		::SetBkColor(hdc, RGB(255, 0, 0));

		EndPaint(hwnd, &ps);
		return 0;	
	}
	return DefWindowProc(hwnd, uMsg, wParam, lParam);
}

But it doesn't work. Anything wrong? Thanks.

[2kaud]

BeginPaint/EndPaint should ONLY be called in the handler for WM_PAINT using them at any other time can have weird results and sideeffects.

So why are you calling BeginPaint() for the WM_ERASEBKGND message??

If you want a dc when not processing a WM_PAINT message, use GetDC() and ReleaseDC().
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

[LarryChen]

So why are you calling BeginPaint() for the WM_ERASEBKGND message??

If you want a dc when not processing a WM_PAINT message, use GetDC() and ReleaseDC().
http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

SO I changed the code,

LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
	HDC hdc;

	switch (uMsg)
	{
	case WM_DESTROY:
		PostQuitMessage(0);
		return 0;
	case WM_ERASEBKGND:		
		hdc = GetDC(hwnd);
		::SetBkColor(hdc, RGB(255, 0, 0));
		ReleaseDC(hwnd, hdc);
		return 0;	
	}

	return DefWindowProc(hwnd, uMsg, wParam, lParam);
}

But it still doesn't work. Thanks.

[2kaud]

If you process WM_ERASEBKGND, then you should return TRUE. See http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

This may be of help
http://stackoverflow.com/questions/2...g-box-win32api

[LarryChen]

If you process WM_ERASEBKGND, then you should return TRUE. See http://msdn.microsoft.com/en-us/libr...=vs.85%29.aspx

This may be of help
http://stackoverflow.com/questions/2...g-box-win32api

Even I return TRUE in processing WM_ERASEBKGND, it still doesn't work. The window looks transparent but I expect it to be red. What went wrong? Thanks.

[VictorN]

SO I changed the code,

LRESULT CALLBACK WindowProc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
	HDC hdc;

	switch (uMsg)
	{
	case WM_DESTROY:
		PostQuitMessage(0);
		return 0;
	case WM_ERASEBKGND:		
		hdc = GetDC(hwnd);
		::SetBkColor(hdc, RGB(255, 0, 0));
		ReleaseDC(hwnd, hdc);
		return 0;	
	}

	return DefWindowProc(hwnd, uMsg, wParam, lParam);
}

But it still doesn't work. Thanks.

Note then WM_ERASEBKND is sent with wParam set to the device context. So you don't need to GetDC/ReleaseDC.

BTW, did you try to handle WM_CTLCOLORDLG?