We are building a new experience for our SmartBear Community.
This site is now read-only. You can still browse and search as usual. Learn More
This site is now read-only. You can still browse and search as usual. Learn More
Ensure your https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/index.html are defined and structured correctly, and make use of https://support.smartbear.com/testcomplete/docs/testing-with/exploring-apps/object-browser/about.html.
1. It could be a slight bug in TC, hence you can't find the object.
2. It's not possible to convert scripts to keyword tests
Once you added the property to MSAA, if you use the Object Spy tool, it should highlight each of the buttons. Object Browser may show you more details, like this
I can't see Ribbon2 being used anywhere 😕 ?
FYI. If you were to add the WndClass property value 'AfxControlBar140' to MSAA (Project Settings), you might be able to access the individual buttons
Thank You!
I do not see Ribbon2 anywhere either. Yet when I run the keyword test is fails with Ribbon2Error. When I look at the script generated from the keyword test I get this: Aliases.draft.wndAfx.Ribbon2.Main.CheckItem(40068, true, false);
I change it to Aliases.draft.wndAfx.Ribbon.Main.CheckItem(40068, true, false); running the script also fails because it does not find Main which is why I insert Aliases.draft.wndAfx.Ribbon.WaitVCLNETObject;
Delay(5000); and save. Now the script succeeds most of the time.
I guess my questions are:
I have found MSAA and added AfxControlBar140. Have not had a chance to play with it yet.