Forum Discussion
AlexanderM
14 years agoStaff
Hello Bill,
The real time of waiting for an object can differ from the Timeout value specified for the WaitWinFormsObject method. Please pay attention to the following remark in the WaitWinFormsObject Method article:
As for the problem with the dockGlobalAssistant object, I recommend that you try handling it as described in the Handling the 'Object Does Not Exist' Error help topic. Does this help?
The real time of waiting for an object can differ from the Timeout value specified for the WaitWinFormsObject method. Please pay attention to the following remark in the WaitWinFormsObject Method article:
Note that Timeout value is not strict and if the tested application is busy, TestComplete could wait for the object for a longer period of time than it is specified by the parameter. The following can cause this:
A call to any WaitXXXObject method causes the object tree to refresh. To update object data, TestComplete may call some of object’s native methods that are accessible only from the application’s thread. When the thread is busy, TestComplete tries to call those methods during some pre-defined time (one second) thus delaying the refresh. There could be several attempts to get the object’s data which could result in a noticeable difference from the Timeout value.
As for the problem with the dockGlobalAssistant object, I recommend that you try handling it as described in the Handling the 'Object Does Not Exist' Error help topic. Does this help?
Related Content
- 4 months agoeykxas
- 5 years agoCapricornus
- 6 years agoISR
- 6 years agoromanmfs
Recent Discussions
- 2 hours agoMW_Didata
- 13 hours agod_gfleetwood92