Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!bloom-beacon!eru!hagbard!sunic!news.funet.fi!fuug!tuura!risto
From: risto@tuura.UUCP (Risto Lankinen)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Windows Subclassing
Message-ID: <1158@tuura.UUCP>
Date: 3 May 91 07:47:27 GMT
References: <1991Apr29.190909.12436@hyper.hyper.com> <1991Apr30.151433.12036@ccad.uiowa.edu>
Organization: Nokia Data Systems Oy
Lines: 25

cadsi@ccad.uiowa.edu (CADSI) writes:

>>[preceding discussion deleted]

>You both realize, of course, Reference 1 of the Windows SDK says, explicitly,
>that you should NOT subclass Window's edit control windows.

Hi!

I've seen it in Ref.manual, too, but I take it to mean that you shouldn't
modify the existing window *classes*, because doing so will affect any and
all windows belonging to that class.  Modifying separate windows, however,
affects only those windows and no other.

In other words, I'd use SetClassXxxx() with anything I've called Register-
Class() for, and SetWindowXxxx() with anything I've called CreateWindow()
for, including edit controls, buttons, etc. which just happen to have their
classes predefined.

Terveisin: Risto Lankinen
-- 
Risto Lankinen / product specialist ***************************************
Nokia Data Systems, Technology Dept *  2                              2   *
THIS SPACE INTENTIONALLY LEFT BLANK * 2 -1 is PRIME!  Now working on 2 +1 *
replies: risto@yj.data.nokia.fi     ***************************************