This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 12%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EE%3C/text%3E%3C/svg%3E)
Would like to ask if someone know which message or function i could hook to 'intercept' a window from being activated by clicking at her 'taskbar button'.
Im hooking explorer.exe but i could not find any useful info yet.
WM_QUERYOPEN and return FALSE
(Tested on Notepad on Windows 10, by subclassing it with a WH_GETMESSAGE hook (DLL)
What tool do you use to monitor winapi messages?
Spy++ : Using Spy++
I saw the messages :
WM_ACTIVATEAPP
WM_NCACTIVATE
WM_ACTIVATE
WM_SYSCOMMAND with SC_RESTORE
WM_QUERYOPEN
Great! I had find that hooking explorer.exe message SwitchToThisWindow works. Its better to hook directly the target app than the taskbar.
Do you also know how to avoid the taskbar window button from getting highlighted?
Is your intent only to prevent a minimized window from being restored?
No my intent is to detect when the user click at the window taskbar button, but being able to differentiate a real user click from the window being minimized/focused because another window got minimized above it.
Help me understand a bit better. Lets say that a process A has foreground window on the desktop. Process B has a window that is below the process A window in the z-order. When the user clicks the taskbar button for process B what do you want to happen? Should the process B window remain covered by the process A window but still be able to receive input? What if Alt-Tab is used to switch between windows? What if the user clicks the process B window with the mouse?
@RLWA32 If i minimize a different window and this gonna cause the target window to gain focus, highlight, activate, then it would be ignored and the target window wouldn't receive any focus/input either be highlighted at the taskbar, (the focus could be set to null, like ::SetFocus(NULL), Alt-Tab the same.
But if the target window is visible (not minimized) and the user click on it, then it would be focused/activated, as long the click was not made in the target window taskbar button.
What I'm trying to do is, differentiate when the window get focused, activated, etc, by a click on her taskbar button than by minimizing another windows.
What is the actual problem you are trying to solve with all of these non-standard window handling objectives?
IIm trying to call a function at the exact moment the user click at the window taskbar button.
Everything that has been described so far has been mechanics. So what problem is solved by calling a function when a taskbar button is clicked?