Solved
Forum Discussion
shankar_r
Community Hero
Possible reason:
- TestComplete runs fast, the object might be slow to get displayed.
To try:
- Use object.WaitProperty("Exists",true) and see what happens.
tristaanogre
6 years agoEsteemed Contributor
I wouldn't use WaitProperty as that requires the object to exist to actually CALL WaitProperty. I'd do a verifcation of the object by calling "WaitChild" or "WaitAliasChild" on the parent object to wait for the control and then verify if the returned value has an Exist property set to true.
- DCat12236 years agoFrequent Contributor
Thank you! This was helpful! I appreciate the response!
Related Content
- 2 months agoD0UG
- 2 years agorkadali
- 5 years agolingling_chiang
Recent Discussions
- 17 hours agoAivanitskiy
- 20 hours agonastester