vthomeschoolmom
13 years agoSuper Contributor
WaitVBObject problem
I have a line of script
set frmStatus = Sys.Process("MyApp").VBObject("frmMain").Window("MDIClient", "", 1).WaitVBObject("frmCust", 3000)
set grdStatus = frmCust.WaitVBObject("GridEXCustomers", 2000)
On the second line, Test complete reports waiting for GridEXCustomers. Forever. I have to kill the app to get out.
So off I go to the help file...
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.
I cannot imagine the object tree is being refreshed. And... busy thread? How do I even know? I use the exact same script elsewhere and the grid is found easily.
Help please!
set frmStatus = Sys.Process("MyApp").VBObject("frmMain").Window("MDIClient", "", 1).WaitVBObject("frmCust", 3000)
set grdStatus = frmCust.WaitVBObject("GridEXCustomers", 2000)
On the second line, Test complete reports waiting for GridEXCustomers. Forever. I have to kill the app to get out.
So off I go to the help file...
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.
I cannot imagine the object tree is being refreshed. And... busy thread? How do I even know? I use the exact same script elsewhere and the grid is found easily.
Help please!