Win class performance, cause (NEW), and a test for all

[DR_LaRRY_PEpPeR]

Again, I'm not trying to USE it, don't worry.

All I'm hoping to do is understand (even for 3.76, whatever) and confirm about all that "extra stuff" I/we talked about that happens otherwise during window creation -- you said it can't be removed, emulates other APIs, etc. and such...

Quite simply, as I've said, I came to the logical conclusion that "extra stuff" (repeated notification messages, etc.) must be to support drag-and-drop, as that's the only functionality that obviously breaks without the "extra stuff." My thought: What else could it be for? Everything else works fine without "extra stuff."


So obviously I'm trying to "get" (or confirm) its purpose, with default settings (e.g. normal configs, NOT about OpenWinClass=#).

[tzuk]

As I said a few times, without going into detail, that extra stuff assists in implementing Win32 hooks. Drag and drop is a different thing and not related.

[DR_LaRRY_PEpPeR]

OK, thanks for debunking my theory that it was related to drag-and-drop...

But that makes me more curious and confused! Regarding that extra stuff assisting implementing Win32 hooks, etc. (yeah, I know you said that a few times, but didn't understand), can you point out something I should see that "breaks" when that hook emulation stuff doesn't happen...?

[tzuk]

I don't have any specific examples, but it should be anything that calls SetWindowsHookEx to place a global hook (in contrast to a hook on a specific thread).