🚀 go-pugleaf

.
In article <59926@microsoft.UUCP> kensy@microsoft.UUCP (Ken SYKES) writes:
>There's a difference between subclassing a window CLASS and a window CONTROL.
>It is okay to subclass a window CONTROL because it is only one instance and
>the control usually belongs to you.  Subclassing a predefined window CLASS
>changes the behavior of ALL controls created after the class has been
>subclassed.
>...
>It is for this reason and possibly others that predefined CLASSES shouldn't
>be subclassed.
.
The Reference Manual -- Volume 1 from the SDK also gave me the impression
that it WAS talking about subclassing windows (not classes).
(Maybe an error? Doesn't matter, I'm subclassing windows anyway!)
.
From 1.2.10 Window Subclassing (page 1-17):
        NOTE:  An application should not attempt to create a window subclass
               for standard Windows controls such as combo boxes and buttons.
.
From Chapter 4 SetWindowLong entry (page 4-416):
        An application should not attempt to create a window for standard
        Windows controls such as combo boxes and buttons.
.
For people who wanted to subclass all instances of a class in their
application only, there was a method described on MS Online a year
or two ago called "superclassing" -- create your own class (like
"mycombobox"), and copy all the info from the standard "combobox"
class to it (except your specialized wndproc).
.
Frank Bielsik
fjb@dhw68k.cts.com