Thread: Best Practice? (Dialog vs .. Not Dialog?)

Well, as i am going through MSDN, trying to gather enough information to start peicing together anything not from a tutorial,

i relized aside from functioning differently (doing little nifty things here and there), Do i need a dialog?

Now dialogs look decent, their structure looks good and all so that may be the reason i use them..
But honestly, all buttons, textfields (user input and program output), combo boxes, lists, ect.. are all just overglorified windows correct? Atleast thats the way theForgers tutorials made me feel. Everything is treated like a window, which makes sense in the most low level aspect, having the parent / child thing going on.

But with all that said, strictly on terms of "Controls" (buttons, textfields(input & output), combo boxes, ect..), is there any advantage to using normal Windows vs Dialog Boxes?

When dealing with a straight GUI, it's totally up to you! Dialogs can be build from resources, and straight windows are generally "coded" instead of created from a resource.

So it's not necessarily about what's better or worse in this case, it's more about what makes sense for the program you're building.

Do I need a dialog

Only you can answer that

hmm, interesting. Given bigger projects, what would you suggest and what for reasons? I assume if i am involving OpenGL i would want a plain window, but without opengl / animation, it seems anything can be done with both of them right? Except some handle messages a bit dif.

And i am still "coding" the resources, as i have no clue what all this visual editor junk is about and if Dev C++ has one lol.