AutoIt and Delphi apps

[r4bbit]

Hi,

I'm new to AutoIt, and I'm trying to use it together with a Delphi app.

The app is actually an installer which can be downloaded here:

http://www.freenew.net/windows/skype/68644/download.htm

I want to write a script which automatically skips all offers.

The problem is that its buttons (next and skip) do not have corresponding window handles.

Here is a screenshot of the installer and WinSpy++:

'>

All I need is to find out the rectangle of the buttons.

Is there any alternative way to handle such Delphi GUIs?

P.S. When I open the file in a resource editor, I can see all those controls.

It seems like Delphi draws them manually instead of relying on Windows API controls.

Thanks in advance for any help.

[MilesAhead]

Is this a third party Delphi program?  I am asking because with Delphi vcl programs the main Window is not the window that handles the message loop.  It is usually TForm1 of type TForm.  You may be able to get the form's parent window handle, then enumerate all children.  But it will likely require quite a bit of trial and error.

Instead of getting the button handles it may be simpler just to send Tab until the button you want has focus.  Then send Enter.

[r4bbit]

Yes, it's a third party program.

As you can see on the screenshot, there are no other parent windows with children.

The application draws the controls manually.

Instead of getting the button handles it may be simpler just to send Tab until the button you want has focus.  Then send Enter.

 

Unfortunately, this is not an acceptable solution. It's too unreliable for my needs.

[mLipok]

off topic:

haha...

awesome avatar 5*

Regards

mLipok

[DonnyF]

In agreement with Miles. VCL can create components on the fly from code (during run-time), but in the end, everything in windows has a handle. You can get the handle of the main form (by title is probably the easiest), and then enumerate the child components (this does not mean child windows, but any component on a form - be it a button, combobox, raidio, etc - is a child component that will have a handle.) If you return the values from the WinAPI, the text of the button that you are looking for should be included. Run a quick enumeration program that stores all child enums in a ListBox or a Memo, and you will be able to grab what you need. The only time it may not return the desired results, would be when the component/button you're trying to get to is in something like a menu. But you should still be able to come up with a quick way to bring up the window using WinWaitActive() or something similar, and then send over a click to the correct X,Y location. If you write an enumration program in Delphi, it's pretty simple to grab what you need from another Delphi program ... or any program for that matter (You may even find buttons that were marked as notVisible from the "sneaky" VB'ers out there). From the info you get, you can convert that over to the language you need (vb, C#, autit, etc).

Cheers,

---D