One Superclass fails but others work

[Michael Mattias]

> just create unique messages like %MYMESSAGE = 10000

Um, I think you should make private messages based on %WM_USER. There's a whole numeric range reserved for application-specific messages.

But if you want UNIQUE and cross-process, see RegisterWindowMessage() function.

[Edwin Knoppert]

Imo if you want to do it right, use WM_NOTIFY with custom NMHDR structure.
It does not conflict with Windows unless you superclass a common control (like treeview and such)
A common control is not a 'standard' control.
The EDIT control is a 'standard' control.

[Chris Holbrook]

Are we 'hobby' or what?

be nice now...

Think logical please..

I try, with a modicum of success...

A windowprocedure is determined for a specific class.

So if you have another class using the same wp, how can you make a difference?

...You probably know what you mean, but hang me if I do.
.