comment on

Impossible to know without seeing the website, but my guess is that the "window" you are trying to control is not a windows native window, but rather some kind of Javascript/CSS 'overlay'. Ie. Instead of the window being made of of Windows native controls, which is required for GUItest to be able to navigate to the correct control by inspecting the window text of the button, that window is just a picture drawn on top the browser window contents.

If so, you won't be able to interact with it using window titles or button labels as they will only exist inside the javascript. The only way GUItest would be able to automate that is by sending a mouse click directly to the appropriate position on the screen.

I do hope for your sake that it's not one of those dratted CSS/Javascript 'floating widgets' that are popping up all over.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

RIP an inspiration; A true Folk's Guy

In reply to Re: Win32::GuiTest for File download by BrowserUk
in thread Win32::GuiTest for File download by mmittiga17

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Don't ask to ask, just ask
	PerlMonks