Sean,

I'm assuming when you called AttachWindowMessage you gave the FilterBy the 
process you wish to monitor.  The IncludeChildren parameter only makes sense if 
you give FilterBy a Window object.  Meaning if you specify a Process or specify 
nothing the IncludeChildren parm is ignored.  Only if you pass in a Window 
object for the FilterBy does the IncludeChildren make sense and used. 

There is no event that fires when a new process is started.  But a process 
without any window is not very useful.  So you could monitor OnChildCreate on 
the Desktop window so any window that gets created would call you.  You can 
then look at the process it is in and do what you want at that point.

Adding the ability to monitor window messages to WEEvent makes the UI much more 
complicated.  Because millions of messages are sent to windows you wouldn't 
want WEEvent to monitor all windows for the message and display the data, it 
likely couldn't keep up.  So that means you would have to tell WEEvent what 
window you really want to monitor and that gets a bit uglier.  So you are left 
just hooking the process and/or window you are really interested in and monitor 
it with your own app.

Doug

-----Original Message-----
From: Scripting 
[mailto:[email protected]] On 
Behalf Of Sean Farrow via Scripting
Sent: Wednesday, February 15, 2017 2:44 AM
To: [email protected]
Subject: Monitoring messages from a window and process start/termination 
notifications

Hi,

I need to monitor messages sent to any window in a particular process. Should I 
be setting the child flag to true or false when doing this?
Also, is there a mechanism to detect when processes start/terminate?
Finally, could the ability to monitor window messages be added to WEEvent, for 
the situation where you don't know what messages you need to monitor, I know 
there's spy++, but it would be nice to have this as a native WE capability.

Any help appreciated.
Kind regards
Sean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com/attachments/20170215/2107319b/attachment.htm>
_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/dgeoffray%40vfogroup.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com
_______________________________________________
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/scripting-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/scripting-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/scripting-window-eyes.com

Reply via email to