The bold messages below inside the main message loop are on my research list because:
- they seem to be undocumented in
WinUser.h and other header files
- they are sent to Window handles that have no corresponding VCL TWinControl bound to them
- they are
WM_TIMER messages sending to a null hwnd, without the Delphi code registering a window-less timer (note the lParam indicates they have different call back procedures attached to them)
Being inside the message loop, they are either posted or created by Windows.
The hexadecimal value for WM_TIMER is documented: [Archive.is] 0x0113 site:https://docs.microsoft.com/en-us/windows/desktop/winmsg – Google Search.
Neither of the below messages are documented in either of the Undocumented Windows books (yes, there are two; the first – though rare to get – was a slightly earlier published one-person effort; the second was a tiny bit later three-person effort, but much thicker and included a diskette with tools; both books complement each other well; I am listed in both):
Messages I am looking for:
Yes, I know that Windows Messages are usually noted as 4 hexadecimal digits, but since they are UINT, the logging framework logs them as 32-bit hexadecimal values as this was a 32-bit application, see these WM_* constants and message ranges:
Note that [WayBack] Which message numbers belong to whom? – The Old New Thing explains more about CreateWindow and RegisterClass, which are important for the above subranges.
Similarly, the sharing of the ID space for Windows Messages, Atom Names and Clipboard Formats:
It might be that two of the messages are related to an undocumented UserAdapterWindowClass: [WayBack] Windows Creators Update Crashes old C++ Apps – Stack Overflow.
On message handling in general:
Related (as my WM_TIMER knowledge was rusty when scheduling this blog post):
Read the rest of this entry »
The Wiert Corner - irregular stream of stuff 