Very Computer

My WinMain calls CreateDialog to create a modeless dialog. I then ShowWindow
and UpdateWindow to display the dialog. Finally, I start the message loop:
        while (GetMessage(hWnd, &msg, 0, 0) > 0) {
                .
                .
                .
        }

Inside the DlgProc if the message is a WM_COMMAND I check the LOWORD(wParam) to
see if the exit button (or close-window button on the dialog frame) has been
clicked. I then call PostQuitMessage(0) and return FALSE from the DlgProc.

This works well.

I've added several controls to the dialog box: static controls, edit controls,
buttons, and list controls. When I add a combo box control to the dialog box,
things stop working properly. If you click the combo box the dialog "hangs."
The list portion of the combo doesn't show, and the only way to regain control
of the dialog is to bring another application to the foreground and then bring
the dialog back up... and even then, I may have to click the Exit button a few
times to fix the problem.

Anybody know what my trouble is? If you want, I can send the code from my
DlgProc.

Thanks!

Jonathan Zimmerman

Quote:> I've added several controls to the dialog box: static controls, edit
controls,
> buttons, and list controls. When I add a combo box control to the dialog
box,
> things stop working properly. If you click the combo box the dialog
"hangs."
> The list portion of the combo doesn't show, and the only way to regain
control
> of the dialog is to bring another application to the foreground and then
bring
> the dialog back up... and even then, I may have to click the Exit button a
few
> times to fix the problem.

> Anybody know what my trouble is? If you want, I can send the code from my
> DlgProc.

For fixing the misbehaving combobox, I'd check you arn't accidently
returning TRUE from the DlgProc for messages you arn't actually handling /
and or ensure that none of the case clauses is falling through to the next
case due to a missing break.

Chris
--
VisualC++ & Win32 FAQ: http://www.mvps.org/vcfaq
My Win32 Page: http://www.mvps.org/user32

Your example has the HWND and LPMSG reversed. I assume this is just a typo.

You won't get any default dialog behavior unless you call IsDialogMessage.

As Chris said, DialogBox would be better if it works for you.

Quote:> Hi,
> I'm fairly green when it comes to straight Win32 programming, so maybe
> the answer to my problem is fairly simple.

> My WinMain calls CreateDialog to create a modeless dialog. I then
ShowWindow
> and UpdateWindow to display the dialog. Finally, I start the message loop:
> while (GetMessage(hWnd, &msg, 0, 0) > 0) {
> .
> .
> .
> }

> Inside the DlgProc if the message is a WM_COMMAND I check the
LOWORD(wParam) to
> see if the exit button (or close-window button on the dialog frame) has
been
> clicked. I then call PostQuitMessage(0) and return FALSE from the DlgProc.

> This works well.

> I've added several controls to the dialog box: static controls, edit
controls,
> buttons, and list controls. When I add a combo box control to the dialog
box,
> things stop working properly. If you click the combo box the dialog
"hangs."
> The list portion of the combo doesn't show, and the only way to regain
control
> of the dialog is to bring another application to the foreground and then
bring
> the dialog back up... and even then, I may have to click the Exit button a
few
> times to fix the problem.

> Anybody know what my trouble is? If you want, I can send the code from my
> DlgProc.

> Thanks!

> Jonathan Zimmerman

Thanks for the help.

Jonathan Zimmerman