Forum Discussion
najes
Occasional Contributor
Finally figured the workaround for this.
So i used the FindChild method instead of the mapping (still not sure why the mapping didn't work tho):
Aliases.MainWindow.FindChild(["WndClass","ControlId"],["Edit",1745],6,true).SetText(100);
Thank you for the replies!
tristaanogre
6 years agoEsteemed Contributor
It depends somewhat on the criteria you are using for the mapping of the dialog. Additionally, there may be a timing issue where you are attempting to act on a window/component before it's available for action. Either one of those could cause behavior where windows and objects are not being recognized and acted on in a timely fashion.
Related Content
- 8 months agomortenb123
- 4 years agoBMD
Recent Discussions
- 55 minutes agoashly