This stupid MFC lost all my code that I wrote for one class function. It combined what I changed with something else and now I have to re-write the code.
Ya know I've spent 2 hours trying to re-work this project all because MS cant seem to program a wizard that:
A. Does not crash.
B. Works as designed
C. Doesn't hose your files
Thanks MS, ya bastards.
heh, ive never seen the point in using MFC, i mean.. you can do it without MFC, even better at times (thats my opinion anyway)..
Btw, are you using VC6? and if so, did you install all the service packs? i dont see why it would combine code from another class
Yeah it's 6 and I installed SP2. I dunno what happened. But I had to backup all my files, re-create the project, copy the portions of the old files into the new files, but not change the wizard source. That was annoying.
Then in my Tiles class I had created all of the code to extract tiles from a larger bitmap - and it lost every bit of it. I don't get it, but now I have to start over.
At least I memorized the code or I'd have to fight with it all over again.
hmm, by SP2 you mean windows xp sp2 right? what about the service packs for visual studio.. i think its up to sp 5 now.. or sp 6, not sure
Yes, I believe VC6 is up to SP6. Not sure how much of the later SP's have to do with MFC though. You should know better than to use MFC by now. If you are writing tools I would look into using C#, super fast and you can learn it quickly as you already know C/C++ Win32. The short time spent learning C# (well you had to spend time learning MFC anyway) will greatly pay off, trust me.
"...the results are undefined, and we all know what "undefined" means: it means it works during development, it works during testing, and it blows up in your most important customers' faces." --Scott Meyers
I use v6 at work and .NET at home.
I don't get crashes due to the IDE (only my code).
I have a habit to press [ALT+F] -> [L] (save all) before a build or run.
>>ive never seen the point in using MFC
Compared to WIN32 (in C / C++)
Faster to develop apps.
Easier to use.
Large code base (inc controls).
Plenty of sites to get help/manual/FAQ.
Can be bypassed to use pure WIN32 if required.
"Man alone suffers so excruciatingly in the world that he was compelled to invent laughter."
Friedrich Nietzsche
"I spent a lot of my money on booze, birds and fast cars......the rest I squandered."
George Best
"If you are going through hell....keep going."
Winston Churchill
I agree with the last 3 points, but the first 2 points are pretty subjective. Many programmers actually believe the pure Win32 API is easier to develop with, since you have the flexibility of designing your own class wrappers.Faster to develop apps.
Easier to use.
Large code base (inc controls).
Plenty of sites to get help/manual/FAQ.
Can be bypassed to use pure WIN32 if required.
Whatever you know more will be faster to develop with and easier to use.
If you master both MFC and the pure API - MFC is faster and easier.
Haven't had that kind of problem with IDE, but I've only ever used it on Win2K with all the service packs.
gg
