Click to See Complete Forum and Search --> : Things I do NOT like in VC++ 6


Thomas Satzinger
April 2nd, 1999, 03:34 PM
There are many really great things in VC++ 6 - and they are working good.
But there are also a couple of things which are not so well done.
For me, the ClassView which updates automatically during editing is really a great idea,
but from time to time my classes disappear or appar twice. So I have to leave VC, start again....
Let me know your experiences with these kind of problems

Torsten Jochem
April 2nd, 1999, 05:27 PM
That's right. I also expierenced such a strange behaviour of VC++ 6.

Well, i always have to delete the *.ncb file of my project, then VC 'refreshes' the classview correctly.
Maybe the problem is solved with ServicePack 1 or 2 for MS VC++ 6...?!

Bye, Torsten.

Thomas Satzinger
April 2nd, 1999, 06:13 PM
Concerning a fix in SP1 / 2, that was my hope as well.
But the fact is that the same encounters with SP2 installed

Dave Smith
July 12th, 1999, 08:05 PM
A debugging gripe... When you reach a breakpoint in your code, and then hit "Go", the execution point arrow (the yellow one) still points to the breakpoint, even though execution has continued. I could SWEAR that this was not the case in prior versions of VC++. Let me know if anyone has a fix for this problem.

mr_nisse
February 16th, 2000, 08:42 AM
Yep, happens to me quite often...sometimes just some classes disappear (the ones I currently edit)
, a bit annoying if you are used to find your way arond the code clicking in ClassView.

Another annoying thing is when you get the message "cannot find implementation" (or something like that) when clicking on a function. This happens when the function definition and the function declaration uses different variable *names* (in .h file : void func foo (int bar), in .cpp file : void classname::func foo (int inpar)).



/* If it can't be done in real world, it can be done in C. */

bharkan
August 3rd, 2000, 12:42 PM
Is it possible to delete the NCB file without closing the workspace?
Thank you

BK

bug_crusher
August 7th, 2000, 04:36 PM
The online help in MSDN used to be linked to a CHtmlView or something in version 5.0. That help was badass! Now the crappy MSDN is in another process where you have to ALT-TAB over to another application entirely just to read help. Also the quality of the documentation in general is way less than it used to be. It seems Microsoft will only make decent documentation from the VB perspective.

Subrato Roy
August 31st, 2001, 12:54 AM
Hi !

I always believed we C++ programmers are always notches above others, not to be detered by minor irritations.
Have you ever tried working on a UNIX based project, messing around with C source files in a vi editor ?
VC++ is a real good environment, maybe Microsoft should do away with many of the frills to keep it compact and fast.

Personally, I find the Class View useless sometimes, it doesn't recognize hand-coded classes anyway.

It is very nice for beginners, but as you gain familiarity with class library, you'll feel lesser urge to use it.

Happy Coding !

______________________________

Subrato Roy
Senior Systems Engineer, Telecom
Siemens, Gurgaon, India
Subrato.Roy@sisl.co.in
http://www.sislindia.com

Jeremy Garrard
August 31st, 2001, 04:28 PM
I've often found the missing class/duplicate class problem can be solved by simply changing the offending class header in some way (ie type a space and then delete it), and then saving it again. Classview then sorts itself out again!

Al Havrilla
September 1st, 2001, 11:40 AM
are you saying that you prefer to program without MFC? Ie .. what used to be called "SDK" windows programming?

thanks
Al

tbscope
September 3rd, 2001, 03:56 PM
I don't like the way to build forms in VC++

I usually program the core of my programs in VC++, put them in a dll and call them in Visual Basic.

VB is much easier to make form-layouts.

nikb
September 13th, 2001, 12:06 AM
The poster specifically mentioned UNIX projects, and editing files with the 'vi' editor.

Windows and MFC is not the ONLY development model on this world. Many serious projects are written without relying on MFC, because MFC is a behemoth, its implementation of various classes (e.g. CSocket/CAsyncSocket) are poor, resulting in poor performance and scalability, and because it is not platform independant.

To answer your question, yes, for SOME applications I prefer to program without MFC, even for some GUI applications. And the sizes of the resulting executables reflects that...

-n