thanks Steve. Chip
-----Original Message----- From: Stephen Clower [mailto:[email protected]] Sent: Tuesday, December 08, 2009 10:52 PM To: [email protected] Subject: Re: ClientInformation.Overlap Chip, The overlap window will not change unless you explicitly change it. It's safe to use it when the launch sequence of an application is predictable and you can always depend on a certain window gaining focus at the outset. But sometimes there are programs which pop up splash screens, invisible progress windows, or other unusual types of controls that Window-Eyes sees and latches on to. The overlap doesn't always have to be a focused window-- just the first window that opened when the application's process was launched. The active window, as you too have discovered, must be focusable, and 9 times out of 10, is likely the window you want to watch. I don't use the overlap window in any of my scripts, and I'm not sure what real advantage there is to doing so versus the active or focused windows. Hope that clears things up some. Steve On 12/8/2009 9:35 PM, Chip Orange wrote: > Steven, > > I've never really understood the overlap window, but I'm not sure why > you're making a point of saying it will never change? I don't see > that J.J. is looking for it to change, I believe he thinks, as I do, > that it should start out being the main window, and so any > onChildClipRendered event hooked on it, should catch all of the clips > written to all of it's children. I think he's sometimes seeing this happen, and other times not. > > J.J., do I have your understanding right? > > If so, I can also add on an earlier version I tried to use the overlap > window on an application-specific window, and found it problematic, to > the point where I switched over to either active window or focused > window (right at the start of my app), and found the one I used to be more reliable. > > I thought I just misunderstood what overlap is for, and moved on. > > Chip > > > -----Original Message----- > From: Stephen Clower [mailto:[email protected]] > Sent: Tuesday, December 08, 2009 8:01 AM > To: [email protected] > Subject: Re: ClientInformation.Overlap > > J.J., > > The ClientInformation.Overlap window will never change unless you > explicitly set it to another window. What you might try is hooking > OnChildFocus from the main window, and when the position window opens, > hook OnChildClipRendered specifically from this window. I've found > that looking at ActiveWindow or FocusedWindow.Parent is usually > sufficient for doing this kind of thing. > > Steve > > > > On 12/8/2009 7:17 AM, J.J. Meddaugh wrote: > > Sorry for the confusion. I have the part where it matches the current > window working. But I'm thinking that perhaps > clientinformation.overlap doesn't always hook the correct events > because sometimes it's set to MDI instead of the TeamTalk window. > I'm having a similar problem for the position users section. I want > to hook OnChildClipRendered but when I hook > > ConnectEvent ClientInformation.Overlap, "OnChildClipRendered", > "myOnChildClipRendered" > > It's not activating for the correct clips. It activates for the main > window, and when the position window is opened, but not when the clips > are written inside that window. > Hope that isn't too confusing. > > > > > J.J. Meddaugh - ATGuys.com > A premier Licensed Code Factory and KNFB Reader distributor > > ----- Original Message ----- > From: Stephen Clower<mailto:[email protected]> > To: [email protected] > Sent: Tuesday, December 08, 2009 7:13 AM > Subject: Re: ClientInformation.Overlap > > What if you use ActiveWindow? I.E. > > If InStr(ActiveWindow.Title, "Part of my title bar") Then > ClientInformation.Overlap = ActiveWindow > End If > > Steve > > On 12/8/2009 5:55 AM, J.J. Meddaugh wrote: > > I have an application script which is watching for the volume > control slider to gain focus and then speak the word "volume" as a > label. > I'm using > > ConnectEvent ClientInformation.Overlap, "OnChildFocus", > "myOnChildFocus" > > to watch for this, and it works 95% of the time. > But every so often when I reload the script, Window-Eyes thinks > that ClientInformation.Overlap is refering to the MDI command handling > window instead of the one for the application. > > I could set ClientInformation.Overlap to the correct window to > watch for, but this would break the script for every minor update of > the software, as the version number is a part of the window title, right? > > Is there something I'm missing, or another event I could hook? I > can be relatively sure of a portion of the Window Title, but there's a > slim chance it could pop up in another application, such as a web page > title window, for instance. > Thanks for any help. > > J.J. Meddaugh - ATGuys.com > A premier Licensed Code Factory and KNFB Reader distributor > > > >
