The Window Hooking Mechanism
The window hooking mechanism, or hooks, also deals with intercepting messages, but at a much broader scope than subclassing. Hooking allows us to intercept messages at various set points within the operating system. For example, we can intercept a message before and after a window has processed it.
There are several different kinds of hooks, each with their own special purpose and location within the operating system. They are:
WH_CALLWNDPROC
|
WH_CALLWNDPROCRET
|
WH_CBT
|
WH_DEBUG
|
WH_FOREGROUNDIDLE
|
WH_GETMESSAGE
|
WH_JOURNALPLAYBACK
|
WH_JOURNALRECORD
|
WH_KEYBOARD
|
WH_KEYBOARD_LL
|
WH_MOUSE
|
WH_MOUSE_LL
|
WH_MSGFILTER
|
WH_SYSMSGFILTER
|
WH_SHELL
|
Hooks, unlike subclassing, can have an application scope or a system-wide scope. By this, I mean a single hook can intercept specific messages within a single application, or it can be set up to intercept those same messages for all applications running in the system. Hooks give us control over the system, which cannot be achieved with subclassing. The following are just a few of the uses for hooks:
Modifying messages sent to dialog boxes, scroll bars, menus, or message boxes
Subclassing a window that resides in a separate process
Creating a macro recorder that can play back the recorded macro as well
Developing computer-based training (CBT) applications
Capturing and modifying mouse or keyboard messages at a system level
Providing a help function key for menu items and message boxes
Creating a utility ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access