Pulling data from AutoIt Window Info programmatically

[NelsonA]

Hello,

I was wondering if it's possible to pull AutoIt Window Info data programmatically?

The reason I ask is that I'm currently using a graphical automation language (Sikuli) to visually interact with a program.

However, Sikuli is a bit slow, buggy and occasionally has trouble locating items (which it was able to locate previously). 

I was hoping I could optimize my automation scripts by using AutoIt. What I plan to do is to initially locate a control using Sikuli.

Rather than click on the control (i.e. a button), I instead plan on hovering over the control and then pulling any relevent AutoIt Window Info control data (as one would would if they un-froze AutoIt Window Info by clickig Options --> Freeze) into an AutoIt program.

By control data, I mean the following: ID, Text, Position, Size, ControlClick Coords, etc.

Question: Is this possible?

I've performed a pretty exhaustive search online but haven't been able to find anything that would allow me to pull AutoIt Window Info control data programmatically.

By pulling control data programmatically, I mean only through an AutoIt script, not through the use of the AutoIt Window Info tool itself or some other tool.

Lastly and most importantly, I need to pull the control data only by hovering over the control (not by using a Control ID or any other sort of handle).

Thank you,

Nelson

[BrewManNH]

Can the Au3Info tool see this information you're looking for? If it can, then a script can. It all depends on what control information you're looking for though as to what is visible and what you can retrieve.

[NelsonA]

Yes, the Au3Info tool (aka AutoIt Window Info) can see the information that I'm looking for.

However the question is, what function calls (any function call would be helpful) is the Au3Info tool using to pull something like the ID, Text and ControlClick Coords of a button?

Thanks,

Nelson

[junkew]

are you writing your script in sikuli or in AutoIT? If in AutoIT then you could also use this

sikuli in itself seems not advanced enough to integrate COM objects into a sikuli script

"Win32com module is written in C. Jython contains all the modules that are originally written in Python, but (Java translations of) only few of the CPython modules that are originally written in native code. Win32com module is not included.

I think Jython's idea is to be pure Java, and interoperation with Microsoft COM modules can't be done in pure Java. It could in principle be implemented using JNI and lots of work, but hasn't been done."

Edited October 4, 2013 by junkew

[NelsonA]

Thank you both for your help, after a bit more research I was able to reverse engineer the Au3Info Tool (aka AutoIt Window Info) and find what I was looking for.

@Universalist: I've actually merged both AutoIt and Sikuli together, so I'm really using both languages for a best of both worlds approach.

Thanks,

Nelson