On Wed Oct 18 18:55:35 2023 +0000, Esme Povirk wrote:
I don't think it's necessary to create the window with the same string type that was used to register the class. The WndProc will be treated as ANSI or Unicode based on which RegisterClass function was used. I'm also not sure the point of testing everything with both ANSI and Unicode WndProcs. The subclassed window proc shouldn't be able to tell the difference except by calling something like IsWindowUnicode.
Mainly just trying to be thorough, given the difference between A/W versions of each function is something I only understand superficially.
Digging into it a bit, it seems like there are different A/W WndProcs for builtin classes. Would it make sense to test each subclassed builtin procedure, e.g first test the one retrieved from `GetClassInfoA`, and then the one from `GetClassInfoW`? Or, do we really only need to test one version of these functions? I guess if these are essentially just thunks into some common window procedure code, we could safely assume A/W versions of the WndProc set the same things.