Counterargument: capture Windows keyboard movements with keyboard hooks

     
I found this article on the Internet and followed the steps below. It did not fully achieve the expected results and did not release the hook.

After many experiments, for creating "standard static link mfc dll" or "standard dynamic link MFCDLL" in VC, messages can only be sent in the window of the program that calls the DLL, hooks can be used to hook messages. Otherwise, if a message is sent in a window other than the calling program, the hook will not be able to hook the message. To hook messages sent in all windows, you must create an "extended mfc dll ".

The above is only my own test result. I still don't understand it as to whether it is correct or why. You are welcome to discuss it and give me an answer.





Note: I have created "extended MFC DLL" and exported class interfaces. Functions exported from non-"extended MFC DLL" are connected.