Sorry GW and Rick, I got this to work in external VBScript, so now I'm just left thinking about my VBA example, but obviously external apps do get events from the WE object model. This is one instance where late-night programming caused me to get it right, instead of screwing it all up (like I did in the afternoon today). Rick, I see the VB code from GW has each object you may possibly want events for, being declared (with events) and stored in it's own variable, and the handlers set to handle events from each of these individual objects rather than trying to do everything off of the main application object. I suspect this is the key to why your first attempt wasn't working correctly, from what I remember seeing of your code. (but I am someone who hasn't used VB ...) Chip
_____ From: Chip Orange [mailto:[email protected]] Sent: Saturday, April 16, 2011 11:22 PM To: [email protected] Subject: RE: A little description of what to use AttachWindowMessage for thanks Rick. I'm not being an external script being run by WE though, I'm actually an external application using the WE object model, and so I shouldn't have to use clientIdentify, but I should be able to have events work (I followed an example from MS showing how they used VBScript to access Word's object model, and have it fire event handlers in the VBScript code). Chip _____ From: RicksPlace [mailto:[email protected]] Sent: Saturday, April 16, 2011 8:20 PM To: [email protected] Subject: Re: A little description of what to use AttachWindowMessage for Hi Chip: I downloaded the new VB.net External script from GW. I had to load up VB.net 2010 Express and set it up with 7.5 and get the settings so WE would work well enough to get started looking at it. It seems to be all there and there seems to be a couple of interesting things that are a little diferent, I think, from my code. I did try and run it but the run failed. A WindowEyes message that ClientIdentify needed to be run at line xxxx I don't have time to look into it yet but will tomorrow or Monday if I can. Anyway, I have the complete puppy that should work and I will let you know what I find. Later Chip and see you Sunday. Rick USA ----- Original Message ----- From: Chip <mailto:[email protected]> Orange To: [email protected] Sent: Saturday, April 16, 2011 4:41 PM Subject: RE: A little description of what to use AttachWindowMessage for Hi Rick and GW, I have to agree with Rick: I wrote an external script in VBA, and I too could not get any of the events I tested with to fire at all (things like onActivate and onChildActivate). even when I setup onChildActivate on the desktopWindow object, which should have been firing every time I changed windows, weren't firing. wanting to be sure it wasn't my VBA environment, I then did the same thing using an external VBScript program running under WSH. no joy with it either. Chip _____ From: RicksPlace [mailto:[email protected]] Sent: Tuesday, April 12, 2011 10:38 AM To: [email protected] Subject: A little description of what to use AttachWindowMessage for Hi: Since my VB.net External script is not processing Window Events - actually it did once but never again through several tests it just wouldn't do it again at all. I was wondering what the AttachWindowMessage Method of the WE Application object is used for.It sort of sounds like it might be a counterpart to the MSAA WatchEvents thingy but I'm not sure. The syntax examples are in VBScript in the manual as far as I can tell so I'm not sure this is for Hosted or External scripts and what it actually does. Thanks: Rick USA
