Re: CEdit white

From:

"Tom Serface" <tom.nospam@camaswood.com>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sat, 31 Mar 2007 20:44:45 -0700

Message-ID:

<7DCC4756-A08E-4316-815D-6B1DF2126D74@microsoft.com>

Of course we do this with all kinds of things. We tell the controls what
text to display, for example. I think we just have a disagreement on style.
To be honest, I have derived controls that I use all over the place ... for
example a CStatic that is easy to change the font or background color. Of
course, the dialog sets the color for the CStatic (derived) in it's
OnInitDialog function.

It could be that it's just convenient. I confess that my focus is more on
making good looking applications that work than it is on the letter of the
OOP laws :o)

Also, in this case the action is not initiated by the parent. The control
asks what color to use and the parent just intercepts the request and fills
in the blank. Unless I'm misunderstanding how it works under the covers.

Tom

"David Wilkinson" <no-reply@effisols.com> wrote in message
news:uxOEgC8cHHA.3408@TK2MSFTNGP03.phx.gbl...

Ajay:

I don't think you did. The control does paint itself, but it asks the
parent for the color. This is non-OOP, but can be convenient in one-off
situations. IMHO, it is different from showing or enabling, because these
actions are initiated by the parent, in a correct OOP fashion.

David Wilkinson