Stop guessing what these things are, don't assume the list you have been given by someone is correct, use the tools provided with Win32::GuiTest to discover what the control IDs actually are. If they're subject to change, you'll need to keep your automation code up to date with any changes to this.
| [reply] |
That is exactly what I am trying to do.
But even Button ID's that are returned do not seem to be clickable.
Even getting third party class refs.
Problem seems to be related to embeded objects.
Those seem to be untouchable.
Will browse the monks archive for related issues and solutions.
Tnx for all the help.
| [reply] |
Perhaps the buttons are in a disabled state for some reason for example, imagine a "Continue" button which is not click-able until a check box marked "I have read, understand and agree to the license agreement" is checked.
It's unlikely that anyone here can help (outside providing truisms) unless you provide more data. You've provided no code or spy.pl output and provide no details of the application you're trying to automate. I suggest this is something you spend time debugging in conjunction with a coworker familiar with the application and automation, in such circumstances asking others to speculate what the problems may be isn't a productive use of anyone's time IMHO.
Update: please mark updates to your posts, read and understand How do I post a question effectively?.
| [reply] |
Let's break this down into steps. First, you need to get the window IDs of the buttons that you want to click on. You've got two routes. Find them yourself using utilities like I had suggested or using Win32::GuiTest to write your own code to dig through the structure of the program. Or you can get the information from the program's source code (or from someone maintaining that source code). I really don't see how you can get around that.
Next, there's the clicking of the buttons. Not trying to be mean here, but have you taken the time to read through Win32::GuiTest's documentation? You keep mentioning only PushButton and MouseClick functions. If you take another look at that documentation, you'll notice that one of the first functions it describes is one called SendMouse.
Again, I'll point you to take a look at the code I posted in Re: Problems with WIN32::GUITEST. Look at the section for the 'mouse' emulation. That section is using SendMouse to click on the buttons. If you run that code, you should see the mouse cursor moving to the buttons. Try using something like that with your code.
If you still can't get the button clicks going, try writing some short code to push buttons on the calc.exe from Windows and you can post that code to get more help on grasping the basics concepts.
| [reply] |
