indows, and who is a
child of whom. Compare some of the names to those in your log.
Hth,
Chip
-Original Message-
From: Rick Thomas [mailto:ofbgm...@mi.rr.com]
Sent: Saturday, March 21, 2015 3:21 PM
To: 'Chip Orange'; 'Window-Eyes Scripting List'
Subject: RE: New
Hi Chip et al: Below is about as simple as I can get and eliminating the
process filter did not help.
So you guys are the pros from Dover, what next?
Will posting the WEEvent lines help?
Which objects or events do you want to see in particular?
Do you want to see the properties for the Overlap Wind
x27;Window-Eyes Scripting List'
Subject: RE: New Visual Studio Script
If it's showing up in the log, then it is firing. So, it must be you're not
using that's showing up in the WEEvent log.
Remember a lot of things could possibly make the clientInformation.overlap
propert
h 21, 2015 1:34 PM
To: 'Rick Thomas'; 'Window-Eyes Scripting List'
Subject: RE: New Visual Studio Script
Hi: The Event handler sub does not appear to be firing but the event is
showing up in the WEEvent log.
Any ideas why or what to try next?
Option Explicit
Dim myMSAA
Rick,
Looks like you're missing the "Set" command in front of windowObj
-Original Message-
From: Scripting
[mailto:scripting-bounces+lists3717=comcast@lists.window-eyes.com] On
Behalf Of Rick Thomas via Scripting
Sent: Saturday, March 21, 2015 12:51 PM
To: 'Window-Eyes Scripting Lis
Hi: The Event handler sub does not appear to be firing but the event is
showing up in the WEEvent log.
Any ideas why or what to try next?
Option Explicit
Dim myMSAAEventSource : Set myMSAAEventSource = MSAAEventSource
myMSAAEventSource.Process = ClientInformation.ApplicationProcess
Dim windowObj
Se
Rick,
when working with Objects you need to use “set” with the assignment operation.
set myWindow = FocusedWindow
Otherwise VB will think the variable is a scaler. This is another advantage of
Chips environment.
dim myWindow as WindowEyes.Window : myWindow = ClientInformation.OverlapWindow
