Forum Discussion

stein_oddvar_ra's avatar
stein_oddvar_ra
Contributor
10 years ago

Using AfxWnd90 or AfxWnd120 to access an MFC UI-element

I've inherited an old TestComplete suite that was developed for the testing of our applications. In one of the test projects there's some interaction with the UI-elements of an application using the a...
  • simon_glet's avatar
    simon_glet
    10 years ago
    Hi Stein,



    Yes Aliases, allow you to simplifiy Name Mapping (NM) paths.



    If you set a Name Mapping property with a wildcard, the corresponding Alias will automatically be updated.



    Please find attached a screenshot of the NM tab with an example of a property WndClass with a wildcard.



    Sincerely
simon_glet's avatar
simon_glet
Regular Contributor
10 years ago
Nope, that won't work.



First off, the way you use Aliases is a bit confusing: if I would do a name mapping of something like AimOS.wndAfx.AfxWnd90.EventImageWindow.AfxWnd90.AfxWnd90 I would end up with a path like this: OS.MainFrame.MainWindow.EventImageWindow.Frame1.Frame2. After that the Alias would like this: OS.MainWindow.EventImageDisplay.



Now back to the AfxWnd*. Every NameMapping, Alias have multiple properties among which you should have WndClass. That is where you will replace AfxWnd90 by AfxWnd*.



You will then still be able to run the following to grap AfxWnd120 UI-Elements:

afxWnd = Aliases["AimOS"]["wndAfx"]["AfxWnd90"]["EventImageWindow"]["AfxWnd90"]["AfxWnd90"];



Sincerely