This is a fairly common problem caused by anything from splash screens
to applications whose initial process launches a secondary window, and
then destroys the initial overlap.
When I run into this, I usually manually determine the window that I'm
interested in, and then when the script launches, I set up a timer that
looks for that window (using something like
DesktopWindow.Children.FilterByClassAndModule("blah", "blah"). When I
find the window, then I go on about my business.
Aaron
On 11/10/2010 10:48 AM, Doug Lee wrote:
I and a coworker of mine have sometimes seen ClientInformation.Overlap
be something other than the top-level window of the application to
which the running script is attached. The latest example involved
ClientInformation.Overlap being a DDI window, which isn't even visible
or part of a UI per se.
Is this a known issue, or am I missing something; and is there a best
practice for how to get the top-level window of the current script's
app?
--
Aaron Smith
Product Support Specialist * Web Development
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
