Re: mfc class wizard problem on visual studio 2005

From:

David Wilkinson <no-reply@effisols.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Fri, 21 Sep 2007 06:10:54 -0400

Message-ID:

<O6vefeD$HHA.1208@TK2MSFTNGP03.phx.gbl>

Bin Tian wrote:

hi, all

    I found a problem of mfc class wizards (VS2005 with SP1). If a class
doesn't inherit a MFC class *directly*, e.g. it inherit a class which
inherit a well-known MFC class directly, you can only add message
handlers by hand. And when you open the properties window of the class,
you see the "Events", "Messages" and "Overrides" window are empty.

    For example:

1. create a new MFC class CMyDoc based on CDocument firstly.
2. create a second MFC class CMyDocEx based on CDocument. Because the
wizards limit the base class to the well-known MFC class.
3. change the base class of CMyDocEx from CDocument to CMyDoc.
Meanwhile, you should also change the base class in message map and some
other stuff.
4. try to use class wizards to add message handler to CMyDoc or
CMyDocEx. you will see the problem.

    Is it a bug or feature of VS2005?? And is there any work-around??

Best regards,
Bin Tian

Bin:

Yes, it is like this in Orcas also. This did not happen in VC6.

I think you should file a suggestion on Connect. How hard could it be
to walk the inheritance tree until you find an MFC base (or not)?

I really think we all need to push to get the IDE back up to the VC6
level in Orcas+1, which supposedly will place a renewed emphasis on
native coding with MFC. Personally I think the quality of the IDE is
more important than adding new features.

--
David Wilkinson
Visual C++ MVP