Problem with certain child window controls

Maybe something with your WM_COMMAND?
Can it be that the child windows are sending WM_COMMAND notifications to the dialog, but your winproc assumes that all WM_COMMAND that have the ID of, let''s say, IDOK, are a button click and that''s where you close your dialog? Just guessing


Goblineye Entertainment
The road to success is always under construction

Btw you''re calling InitCommonControls()/InitCommonControlsEx() on startup?


Goblineye Entertainment
The road to success is always under construction

Actually I wasn't using neither of those. I forgot to mention that I'm trying to do these in a dialog box. I created in the resource editor and created it with code (and used those commands) and the dialog still exits when pressed. Don't have a problem with these in a standard Win32 app.

Actually It has to do something with WM_COMMAND. I comment that out of the program and I can click them without killing the app. Only thing I'm checking for in WM_COMMAND is if three buttons are pressed. Each button and the list box has its own name.

[edited by - darkchrono4 on August 11, 2002 4:19:20 PM]

Ok actually I figured out my problem but don''t understand it. For some reason when I''m pressing the list box its call WM_DESTROY. I take that out and the program runs fine. Any ideas on this one?

Anybody?

Can you post your winproc? Or if you want, email me your complete project or just the relevant part and I''ll have a look at it.


Goblineye Entertainment
The road to success is always under construction