Re: Which messages should I delegate?

From:

"Doug Harrison [MVP]" <dsh@mvps.org>

Newsgroups:

microsoft.public.vc.mfc

Date:

Wed, 28 Jun 2006 10:05:48 -0500

Message-ID:

<kg65a2tf3k7fvvsijk4flc4lcktrv1l91g@4ax.com>

On Tue, 27 Jun 2006 17:48:04 -0700, Juan Dent <Juan_Dent@nospam.nospam>
wrote:

Hi,

This seems like a tough one. I have placed one dialog embedded as a child
for each tab item in a tab control. However I need everything to work as
before, i.e. as when all the controls now contained in the dialog (per tab)
were rather contained directly by the CView subclass. -- You know, dealing
with the little real support MFC has for tabbed controls.

Which messages should I send the CView class and which should I process in
the dialog?

One thing seems clear: all notifications from child controls should be
relayed to the CView class. Yet, there are so many possible notifications...

The classes for the individual tabbed dialogs should deal with the controls
they contain. Only you can decide the notifications you need to relay. For
example, if the view (or attached document) has a modified flag, then the
tabbed dialogs should detect the various "changed" notifications sent by
their controls and call the appropriate function in the view (or document).
You can decouple this from the actual type of the target object by using
Windows messages (suitable for the view, but type-unsafe) or interfaces
(suitable for any C++ object, and type-safe).

--
Doug Harrison
Visual C++ MVP