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] <mailto:[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


Reply via email to