[RESOLVED] WM_CREATE and HWND issue

[int Kev]

case WM_CREATE:
		if (hwnd == childwindowHandle)
		{
			
			x = TRUE;
			
		}

x is never set to true.

This is a child window. This case is in the message switch for the child window's message procedure. There are multiple children of the same class. The child windows are created drawn and functional. This logic exactly works in other cases such as WM_PAINT and WM_LBUTTONDOWN and other logic making referencing the parameter hwnd also has no problems.

Why for WM_CREATE, when in the documentation it states that WM_CREATE is called after window creation but before window visibility, does hwnd not evaluate to the handle of the created window?

---

Thank you guys, First post ^_^
-Kev

PS. I don't have permission to create tags on this forum but there's no WM_CREATE tab!

[VictorN]

case WM_CREATE:
		if (hwnd == childwindowHandle)
		{
			x = TRUE;
		}

x is never set to true.

Did you check whether this code is executed?

[int Kev]

Did you check whether this code is executed?

This was me checking! Thank you for replying victor, but I'm not sure what you mean. How else can I check for code execution? Should a WM_CREATE msg not be sent to my window procedure upon window creation? And should, too, the code within it's case not then execute?

[int Kev]

Other code formerly in this WM_CREATE case executed just fine. Just not if checking the window handle.

[VictorN]

This was me checking! Thank you for replying victor, but I'm not sure what you mean.

just set a breakpoint at the line with

case WM_CREATE:

and start debugging (F5)...
Then press F10 to step through the code and look at the debugger ("auto" or "watch") window to see the values of the variables.

[int Kev]

What a useful tool! What appears to be happening is that, although the window was created with
childwindowHandle = CreatewindowEx(... etc, assignment happens after any functions on the right finish.
The CreateWindowEx() function runs, a WM_CREATE message is sent and processed, all before the variable childwindowHandle ever gets an assignment, and so, of course hwnd != childwindowHandle.
Victor, this has clarified many things. Thank you.
I've more to figure out, but as far as I'm concerned, thread resolved.

[VictorN]

...
Victor, this has clarified many things. Thank you.
I've more to figure out, but as far as I'm concerned, thread resolved.

You are welcome!
And now you can use the Thread Tools (the button on the toolbar above the posts to Mark Thread Resolved.

[OReubens]

that code makes no sense...

this message is sent to the CHILD window after the window is actually created. so hwnd is that of the newly created child window.
however, your application has no yet had an opportunity to actually know what the new window handle is, because that's exactly what createwindow is for, to inform you that the OS made a window and "here's the new handle for it"

so how would childwindowHandle possibly have the right value if this is the first opportunity (other than hooking) your app gets to know about the new handle.