On Mon Oct 23 12:52:08 2023 +0000, Connor McAdams wrote:
I didn't include it in the tests, but locally I've tested whether or not you can change the real class for an HWND after it has been set, e.g setting it to edit by passing the HWND to the edit control window procedure, and then passing it into the static control window procedure. It's only able to be set once. If we did your suggestion, this would technically break. So it serves two purposes, avoids unnecessary server calls, and avoids setting it to something else after it has already been set.
I see. In that case, it would be nice to leave an one-liner comment to describe that. That, or `ERR()` if the real class is already set.
Note that normal apps (subclassing applications, WinForms) won't trigger the `ERR()` path. Misbehaving apps will, but we can skip testing for this until such an app appears.