StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20554537
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2013-12-12T21:23:22.767
FavoriteCount
0
LastActivityDate
2013-12-13T02:35:46.393
LastEditDate
2013-12-13T02:35:46.393
LastEditorUserId
65863
OwnerUserId
65863
ParentId
20552523
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
To detect a button press in another process, you have to hook that process. You have four choices for doing that: <ol> <li>use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644990%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsHookEx()</code></a> to install a <code>WH_CALLWNDPROC</code> or <code>WH_GETMESSAGE</code> hook into the target process to catch the <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/bb761825%28v=vs.85%29.aspx" rel="nofollow"><code>WM_COMMAND/BN_CLICKED</code></a> message that is sent to the button's parent window when the button is clicked. The message identifies the <code>HWND</code> and ID of the button that was clicked. The hook must be implemented in a DLL so it can be injected into another process.</li> <li>use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd373640%28v=vs.85%29.aspx" rel="nofollow"><code>SetWinEventHook()</code></a> to catch the <code>EVENT_OBJECT_INVOKED</code> event when the button is clicked. The hook callback identifies the <code>HWND</code> and ID of the button that was clicked. The hook should be implemented in a DLL so it can be injected into the target process for better performance, but is not required. If you do not use a DLL, the hooking thread must have a message loop to receive the events as they will have to be passed across process boundaries.</li> <li>use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644990%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsHookEx()</code></a> or <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms682437%28v=vs.85%29.aspx" rel="nofollow"><code>CreateRemoteThread()</code></a> to inject code into the target process and have that code then subclass the button's parent window using <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644898%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsLongPtr(GWL_WNDPROC)</code></a> or <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/bb762102%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowSubclass()</code></a> in order to catch the <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/bb761825%28v=vs.85%29.aspx" rel="nofollow"><code>WM_COMMAND/BN_CLICKED</code></a> message that is sent to that parent window.</li> <li>use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee684009.aspx" rel="nofollow">UI Automation</a>. Create an instance of the <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee671406.aspx" rel="nofollow"><code>IUIAutomation</code></a> interface using the <code>CoCreateInstance()</code> function, then use the <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee671534.aspx" rel="nofollow"><code>IUIAutomation::ElementFromHandle()</code></a> method to get an <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee671425.aspx%2a" rel="nofollow"><code>IUIAutomationElement</code></a> interface from the button's <code>HWND</code> (or obtain the button's <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee671425.aspx%2a" rel="nofollow"><code>IUIAutomationElement</code></a> interface through other means), then use the <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee671508.aspx" rel="nofollow"><code>IUIAutomation::AddAutomationEventHandler()</code></a> method to subscribe to the <code>UIA_Invoke_InvokedEventId</code> event for that button.</li> </ol> If you have the <code>HWND</code> of the target button, you can use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms633522%28v=vs.85%29.aspx" rel="nofollow"><code>GetWindowThreadProcessId()</code></a> to retrieve the button's process ID and thread ID. You will need the button's parent window <code>HWND</code> (which you can get using <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms633510%28v=vs.85%29.aspx" rel="nofollow"><code>GetParent()</code></a> if needed) in order to use <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644898%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsLongPtr(GWL_WNDPROC)</code></a> or <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/bb762102%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowSubclass()</code></a>. <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644990%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsHookEx()</code></a> and <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd373640%28v=vs.85%29.aspx" rel="nofollow"><code>SetWinEventHook()</code></a> allow you to specify the specific thread ID to hook (and in the case of <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd373640%28v=vs.85%29.aspx" rel="nofollow"><code>SetWinEventHook()</code></a>, the specific process ID as well) so you can minimize overhead used in hooking. <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms682437%28v=vs.85%29.aspx" rel="nofollow"><code>CreateRemoteThread()</code></a> requires the target process handle, which you can get with <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms684320%28v=vs.85%29.aspx" rel="nofollow"><code>OpenProcess()</code></a> using the process ID. So, as you can see, what you are asking for is not going to be trivial to implement. In my opinion (not definitive), the order of techniques from easiest to hardest, in terms of coding, would be: <ol> <li><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd373640%28v=vs.85%29.aspx" rel="nofollow"><code>SetWinEventHook()</code></a> without a DLL (but at the cost of affecting performance).</li> <li><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ee684009.aspx" rel="nofollow">UI Automation</a>.</li> <li><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644990%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsHookEx()</code></a>, or <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/dd373640%28v=vs.85%29.aspx" rel="nofollow"><code>SetWinEventHook()</code></a> with a DLL.</li> <li><a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms644990%28v=vs.85%29.aspx" rel="nofollow"><code>SetWindowsHookEx()</code></a> because of the extra injection code and subclassing</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POCorrectly receive messages from button
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USRemy Lebeau
UserOwnerUserId
1. USRemy Lebeau
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POCorrectly receive messages from button
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.