generic tips before I fall off the deep end

I am just starting to realize how the WinApi really works, and I am realizing that there is a whole lot of coding involved.
Correct me if I'm wrong, but you need to create a new window for everything that the user can click on the screen, you have to set up its properties, register, and show each window. then you have to have a procedure for each window and supply coding for its wm_command message.

that is what I know so far, correct me where i'm wrong, or clarity or add to what I said.

Also how do you people organize your code for winapi? Do you have a .h and .cpp file for each window, and then have winmain in main.cpp?

Yep - you got it all right. :) Fun isn't it ?

Except you don't have to call ShowWindow on each and everyu window/button etc... Set the WindowStyle WS_VISIBLE that does it for you.

For code organisation... erm.. I guess You'll have to figure that out by yourself. I have around 10-20 files for a project...

Quote:

---

Also how do you people organize your code for winapi? Do you have a .h and .cpp file for each window, and then have winmain in main.cpp?

---

something like that, yeah, although I tend to make everyting in c++ classes.. dunno if it's good
/btq

If you are not using C++ use .c files instead. Will save some common errors (" 'C' type cast required" for SelectObject() is the most common)