The problem is probably that you are relying on one of the MFC 3.x and earlier registered window classes for the class name passed to your ::Create(). For example, a very popular way to create a window with a white background is to use "AfxViewOrFrame". In MFC 4.0, not only have all of the window class names been changed, but they also happen dynamically when needed!
The solution is to use AfxRegisterWndClass() and pass the results to Create(). Be sure to specify the right flags to get the desired results. Also check out tech note number 1, which has been revised for 4.0.
- scot@stingray.com, 1/20/96
To test and see if you have the problem:
The control ID's ARE in the message map property page but not on the member variables property page! Huh?
The fix:
The fix is to change the language property of the dialog template (highlight the name of the dialog box in the resource window and click right mouse button). For me I had to change the language property from English (US) to English (Australian), only after doing this do the member variables of control's appear. I assume this property must match your Win95 chosen language, in any case the change fixed it for me and a German user who had the same problem.
doug@psy.uwa.edu.au, email, 12/13/95
I haven't personally experienced these problems, but here's some solutions (some are probably wives tales) for solving the problems:
The APIs used for the Component Gallery have not been made public yet by Microsoft.
It is widely known (at least everyone I talk to) that the VC++ 5.0 help system is very very bad! Microsoft replaced the wonderful, speedy RTF based WinHelp viewer system with an HTML based IE viewer system. Why is it slow? Well now you have to basically have a Alta Vista on your desktop to search since it is basically HTML. There is an indexing system, it is suppose to get better, but it is really bad right now.
Here's what I do…
Sounds cheesy and it is, but the 5.0 help is really that bad if you are a heavy user like I am (not sure if that is a good or bad thing).