Control problems.. where are they?

Can someone give me some insight as to why this will display no error message, nor will it display the actual control? I am doing this in the WM_CREATE message of my main windows message handler. Here is one of the controls I'm trying to create:

Code:

if( (hcowner = CreateWindow("EDIT", "", WS_VISIBLE | WS_DISABLED | WS_CHILD | WS_CLIPCHILDREN, x, y, 200, 40, hwnd, NULL, g_hInst, NULL)) == NULL )
			{
				sprintf(error, "Could not initialize controls. (Error Code: 0006; %u)", GetLastError());
				MessageBox(NULL, error, "Error", MB_ICONEXCLAMATION);
				return(0);
			}

the x and y values have been set according to the GetClientRect() call and - or + values to the returned co-ords from that call.

Any help is appreciated,
Tyouk

Your edit control is being created but, with the WS_DISABLED style, is probably invisible against the parent's background (a disabled edit control's background colour defaults to COLOR_BTNFACE, see GetSysColor). For testing purposes you might consider giving the control a border style (or extended style if using CreateWindowEx) or setting some text via the lpWindowName of CreateWindow/Ex; that way you'll at least have a visual cue of the window's existence.

The problem isn't with the background. I am also creating STATIC controls in the same method and it's still not producing anything for me. I see no text, even though I have set text (no point to creating a STATIC control without text).

why don't you post some more code. Maybe that will elicit more help.

The problem isn't with the background. I am also creating STATIC controls in the same method and it's still not producing anything for me. I see no text, even though I have set text (no point to creating a STATIC control without text).

Pity: I was fairly certain that, given the code and description you had supplied, the control was being created but was simply not visible.

If you haven't already done so, here's some things to check:

• IsWindow on the parent handle and the return value from CreateWindow.
• Is g_hInst valid? Try replacing it with GetModuleHandle(0).
• Replace x and y with absolute values.
• Create a small, test windows application that uses similar code to create these various controls. Can you replicate the problem with this example?

If you still have problems then post the test example code; if you work out what the problem is then post a description of the solution so that others may benefit.

Good luck and Happy New Year.

Okay my problem was with the x and y values. I tried each of your suggestions (from top to bottom) and as soon as I got to that, I now can see one of the controls. I guess when I called the...

Code:

RECT rect;

GetClientRect(hwnd, &rect);

It's values were messing things up. I'm going to see what values are returned from that call and see what I can do from there. The x and y values where being determined in a fashion such as:

Code:

x = rect.left + xlspace;

xlspace was a value determined based on how far from the left this control needed to be placed, but I think I could just place xlspace in the parameter where it asks for the x value because from what I can tell it would place it exactly where it needs to go

I'm trying to keep the controls relative to a certain position on the screen (and during WM_SIZE messages I am calling the MoveWindow() call in order to make sure that the controls stay relative to the same spots so then the look stays the same).

Thanks for your help,
Tyouk

Ummmm....

your using the CHILD style but not setting the controls ID number (you set them all to NULL). This may cause problems as multiple controls of the same parent can/should not have the same ID number.

cast the HMENU param to a #define ID number

#define IDC_SOME_EDIT 30001

CreateWindow(........., (HMENU)IDC_SOME_EDIT,.....)

Ya I was going to get to that a little bit later. Didn't think it was that important to have them all ID'd right off the bat.

I'll add that though. I got them visible already though.

Thanks,
Tyouk