Im a C++ programmer just entering the world of MFC and MSVC++
i have made an empty dialog project. Now i know in what file to put main() (.cpp hope its still that way in this) but in all the jumble of pre-generated code i dont see main() am i just to put it in the bottom after everything or...? thanks for any help with it
=@-OmegatronO-@=
In a GUI Windows app, there is not a main() instead, there is a winmain().
I would advise you to learn at least the basics of the API before fiddling with MFC. There are others who would disagree of course, there always are.
The wizard generated code is crap, and in some cases, will not even compile.
Start with this...
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
Okay, so don't take my file! Try again...
Wave upon wave of demented avengers march cheerfully out of obscurity unto the dream.
In MFC WinMain is hidden away in the MFC libraries......I havent looked at it for a while, but if I remember rightly, WinMain calls AfxWinInit and also calls AfxGetApp which returns the reference to the global application object you create with an MFC app. So all you have to do is create this global object and you are fine - WinMain is handled
If you are really interested in whats going on under the hood with MFC then to start with peruse the articles at codeproject about it. hang on ill dig up a link .Thats just 1 there are other articles. There is a good book on this also called MFC internals but that is probably overkill unless you are a hardcore mfcer
Free the weed!! Class B to class C is not good enough!!
And the FAQ is here :- http://faq.cprogramming.com/cgi-bin/smartfaq.cgi
Well looking at the interworkings of MFC seems a little counter-productive. MFC exists so you don't have to deal with WinMain() or thinking. Maybe if I ever used MFC I'd take a different side here but if there is something that you are just plain not being able to accomplish via MFC the API is sitting right there ready to be used too.
I dont think it's that clean cut....sometimes NOT using MFC is difficult (if you are creating ActiveX apps for instance). All that boilerplate code is very hard to do without.
And if you use MFC enough, then a peek at the insides is very usefull....same as knowing how the STL implements a std::list - maybe no essential, but a benefit if you know how it works
Fair enough, though I find that I use wxWindows much more frequently than I use MFC. Of course I'm shooting myself in the foot with this example since I find myself looking into wxWindow's source whenever I use it. The ActiveX issue is really the only thing that ever makes MFC necessary.
Damn you master!!!Originally posted by master5001
ActiveX issue is really the only thing that ever makes MFC necessary.
Your not baiting me with that one!
