C / C++ / MFC

3-Aug-03 6:07

Hello -

I have a CWnd derived class which I am creating in a MFC SDI app. I create it hidden, and its job is to handle some messages generated by the back end of my app. If I fire up the app and don't touch it, everything runs fine, and all messages are received by this class. However, as soon as I start doing anything in the GUI (i.e. more messages are generated), then some of messages generated by my back end are posted but not received.

Here is how I create the class:

m_pMyWnd->CreateEx(0, _T("STATIC"), _T(""), 0, CRect(0,0, 100, 100), NULL, 0);

and another chunk of code does a postmessage to this window, but it doesnt receive the message, even though PostMessage() succeeds.

Is there a different way I should create this window to ensure that my messages will make it through?

Thanks!

Marcus Spitzmiller

"Why must life be so hard? Why must I fail at every attempt at masonry?" - Homer

Cathy3-Aug-03 7:59

Cathy

3-Aug-03 7:59

It sounds like you really want a multi-threaded application.

Cathy

Life's uncertain, have dessert first!

Marcus Spitzmiller3-Aug-03 8:08

3-Aug-03 8:08

Care to explain? This app is quite multi-threaded already, and the section posting the messages is in its own thread...

Marcus Spitzmiller

"Why must life be so hard? Why must I fail at every attempt at masonry?" - Homer

Cathy3-Aug-03 13:48

Cathy

3-Aug-03 13:48

I thought maybe that was the problem, that you were doing it in the same thread.

I had to do something like this to get my messages through:

<br />
while (theApp.m_pMainWnd && PeekMessage(&msg, theApp.m_pMainWnd->m_hWnd, 0, 0, PM_NOREMOVE))<br />
{<br />
	if (!theApp.PumpMessage())<br />
	{<br />
		PostQuitMessage(0);<br />
		return TRUE;<br />
	}<br />
}<br />

Cathy

Life's uncertain, have dessert first!

Joe Woodbury3-Aug-03 9:14

Joe Woodbury

3-Aug-03 9:14

First, messages sent though PostMessage are not guaranteed to make it through. In practice, however, only in very extreme circumstances (slow machine, fast input) do they not get through.

Also note that PostMessage() will only fail if the window handle is incorrect or some other critical problem. Whether or not the message will be received has no bearing on the success of the call. (See SDK documentation.)

I question the use of a hidden window. I suspect the messages are being reflected somewhere. Why not just use the main window and use USER messages?

Marcus Spitzmiller3-Aug-03 10:37

3-Aug-03 10:37

Joe,

Thanks for the info.

I suppose I should've mentioned that the messages I'm referring to come from the WaveOut API, so they cannot be user messages. In particular, I'm handling the MM_WOM_DONE message. (See waveOutProc in the SDK doc, if you are interested.)

The reason I chose to not use the main window was for code maintainability. I am able to keep all of the waveOut code in one or two classes that I can move around as needed, this way. I'm not sure that handling it in the main window will do it either, see below...

You are correct about the messages being reflected, I think. I've noticed that the MM_WOM_DONE message comes through my main message loop and is then dispatched to this hidden class, most of them anyway. (Hence my problem - I'm not seeing all of them here, either.) Based on the way I'm creating the window (see the code in the prior post, parentwnd = NULL), I figured that the messages would come straight to this window,but I guess not.

So assuming that this is the nonUSER message I'm working with, is there a way to get it to post to the queue in my hidden window directly, instead of routing through the main message loop?

Thanks!

Marcus Spitzmiller

"Why must life be so hard? Why must I fail at every attempt at masonry?" - Homer

Joe Woodbury3-Aug-03 18:11

Joe Woodbury

3-Aug-03 18:11

I have a wave in/out class that doesn't have a problem.

First, due to where the code is used, I don't use MFC when I create the callback window. I also create it with CreateWindowEx with WS_EX_NOPARENTNOTIFY. Here's a snippet from my code:

LRESULT CALLBACK CBWaveCallback(
	HWND    hwnd,
	UINT    msg,
	WPARAM  wParam,
	LPARAM  lParam)
{
	CBWave *pWave = (CBWave *)::GetWindowLong(hwnd, 0);
	if (pWave)
	{
		switch(msg)
		{
			case MM_WOM_DONE:
				pWave->OnDataOut((HWAVEOUT) wParam, (WAVEHDR *) lParam);
				return 0L;

			case MM_WIM_DATA:
				pWave->OnDataIn((HWAVEIN) wParam, (WAVEHDR *) lParam);
				return 0L;
		}
	}

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

static TCHAR nameBase[]	= _T("CBWaveCallback");

HWND CBCreateWaveWindow(
	HINSTANCE hInst,
	HWND hWndParent,
	LONG waveClassThisPtr)
{
	TCHAR className[32];
	_tcscpy(className, nameBase);
	_tcscat(className, _T("Class"));

	WNDCLASS wndClass;
	if (!::GetClassInfo(hInst, className, &wndClass))
	{
		wndClass.style         = 0;
		wndClass.lpfnWndProc   = CBWaveCallback;
		wndClass.cbClsExtra    = 0;
		wndClass.cbWndExtra    = 4;
		wndClass.hInstance     = hInst;
		wndClass.hIcon         = NULL;
		wndClass.hCursor       = NULL;
		wndClass.hbrBackground = NULL;
		wndClass.lpszMenuName  = NULL;
		wndClass.lpszClassName = className;

		if (!::RegisterClass(&wndClass))
			return (HWND) 0;
	}
	TCHAR windowName[32];
	_tcscpy(windowName, nameBase);
	_tcscat(windowName, _T("Window"));

	HWND hWnd = ::CreateWindowEx(WS_EX_NOPARENTNOTIFY, className, windowName,
									hWndParent ? WS_CHILD : WS_POPUP, 0, 0, 0, 0, hWndParent, NULL, hInst,	NULL);

	::SetWindowLong(hWnd, 0, waveClassThisPtr);
	return hWnd;
}

Marcus Spitzmiller4-Aug-03 3:20

Flat CComboBox and CIPAddressCtr

4-Aug-03 3:20

Thanks for the help! I'll give that a try.

Marcus Spitzmiller

"Why must life be so hard? Why must I fail at every attempt at masonry?" - Homer

Eugene Pustovoyt3-Aug-03 5:41

Eugene Pustovoyt

3-Aug-03 5:41

Hi,

How can I create the controls CComboBox and CIpAddressCtrl without edges.
Removes a WS_BORDER style has not effect.

Best regards,
Eugene Pustovoyt

PJ Arends3-Aug-03 8:45

PJ Arends

3-Aug-03 8:45

Have you tried removing the WS_EX_CLIENTEDGE extended style. You may have to call RedrawWindow with the RDW_FRAME flag to force the change.

Sonork 100.11743 Chicken Little

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

Within you lies the power for good - Use it!

Eugene Pustovoyt3-Aug-03 9:07

Eugene Pustovoyt

3-Aug-03 9:07

Thank you for quickly answer.

I tried create two classes FlatIpAddressCtrl and FlatComboBox.

In the PreCreateWindow method add next line

cs.dwExStyle &= ~WS_EX_CLIENTEDGE;

But I still see a edge.

Best regards,
Eugene Pustovoyt

PJ Arends3-Aug-03 9:24

PJ Arends

3-Aug-03 9:24

Are you using these controls on a dialog, property sheet, or form view. If so, then apply the change in the PreSubclassWindow() function. If you put a breakpoint in PreCreateWindow() you will find the function is not called.

Sonork 100.11743 Chicken Little

"You're obviously a superstar." - Christian Graus about me - 12 Feb '03

Within you lies the power for good - Use it!