Sign in to follow this  
Followers 0
ntgd83

Legacy MFC application

2 posts in this topic

Hi,

Recently, I have to use AutoIt script to drive an legacy MFC application. When I use AutoIt v3 Window Info tool to look at the listview wndow, it looks something like this:

>>>> Control <<<<

Class: SysListView32

Instance: 3

ClassnameNN: SysListView323

Advanced (Class): [CLASS:SysListView32; INSTANCE:3]

ID: 59648

Since it does not return an unique app.ID number like what I used to get with more current application created by .net, e.g.

>>> Control <<<<

Class: WindowsForms10.MDICLIENT.app.0.2e0c681

Instance: 1

ClassnameNN: WindowsForms10.MDICLIENT.app.0.2e0c6811

Advanced (Class): [CLASS:WindowsForms10.MDICLIENT.app.0.2e0c681; INSTANCE:1]

ID: 1773694

I usually put "CLASS:WindowsForms10.MDICLIENT.app.0.2e0c681; INSTANCE:1" in my autotestini.ini file. How can I make my AutoIt script to drive the legacy MFC Visual C++7.1 program ?

I tried using "CLASS:SysListView32; INSTANCE:3" in my autotestini.ini file, it did not work.

Share this post


Link to post
Share on other sites



Did you correctly ID the window?

What exactly did you try to do with the listview? Are you sure whatever it was is valid with the older version? If you do ControlGetHandle() with your window and control identies, do you get the valid handle back?

:blink:


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0