Forum Discussion
The problem may not be with the specific panel but with the parent. Can you confirm that wndWindowContent is available as well? Because the waiting may not be for the child object itself but for the parent.
Yes I can confirm that wndWindowContent is present. This is a very top level element that is pretty much always present. For giggles I stopped the execution of a test at this point in code and confirm with the highlight element that it is present and very quickly identified.
- AlexKaras5 years agoChampion Level 3
Hi,
> Aliases.browser.pageMain.wndWindowContent.WaitAliasChild("panLogin", ProjectSuite.Variables.TinyWaitTimeout);
> wndWindowContent is present. This is a very top level element [...]
This might be the reason depending how panLogin alias is mapped.
Guessing that if it is mapped using Advanced Find, then TestComplete will drill-down complete objects tree in order to check if the sought for alias exists.
The more definite and precise identification criteria and search path are defined in NameMapping, the more fast .WaitXXX() method will work.
- vthomeschoolmom5 years agoSuper Contributor
So I am guessing by Advanced Find you mean extended search? It WAS using extended search. And it did not need to. I removed the selection of extended search on wndWindowContent. I confirm that it is still found properly. That element is used all over the place and does not take a long time to find. panLogin, when present, is found immediately. When NOT present, the timeout is not being honored. That is the crux of my issue.
Thanks
- vthomeschoolmom5 years agoSuper Contributor
I replaced the WaitAliasChild with FindChild and properties. It is much faster. Still kinda wonder why WaitAliasChild is taking so long. I want it to timeout when I want it to! I don't love the FindChild in this case since it mimimizes the effectiveness of reuse of a well constructed NameMapping. Ah well. Such is life.
Related Content
- 6 years agorizzomeister
Recent Discussions
- 5 hours agoSvetaG