WaitNamedChild fails to find object
I'm using this method to find mapped objects in an MFC application, in various cases, it fails to find the object even though it's there. Seems it's when parent object has WndClass #32770. For all pop...
Forum Discussion
Hi Robert,
Here's an example:
I've 'Report' where Report is #32770 class.
I use WaitNamedChild to get Print Button in 'Report' - mapped name - 'Print' - properties mapped with - objecttype = Button, objectidentifier = Print. There is only one child with these properties. (screenshot attached)
validate after this call doesn't exist: validate = parent["WaitNamedChild"](name, 0); (where parent is Report object and name is "Print")
As a workaround, I call FindChild, two properties, visible, mappedname, depth=0. Report can have anywhere from 20-70 children, so this is quite slow, but finds it all right. So far, I've seen this fail only when parent is class #32770, but not consistently.
If I call WaitChild for this same object it finds it all right. Also, I called WaitNamedChild in TestComplete directly, exact same parameters, and it worked.
I'm using connected application - C#, I tried the same in VB.net, just in case, but same result. It appears there is a problem only when using this with connected app.
Thanks.
Here's an example:
I've 'Report' where Report is #32770 class.
I use WaitNamedChild to get Print Button in 'Report' - mapped name - 'Print' - properties mapped with - objecttype = Button, objectidentifier = Print. There is only one child with these properties. (screenshot attached)
validate after this call doesn't exist: validate = parent["WaitNamedChild"](name, 0); (where parent is Report object and name is "Print")
As a workaround, I call FindChild, two properties, visible, mappedname, depth=0. Report can have anywhere from 20-70 children, so this is quite slow, but finds it all right. So far, I've seen this fail only when parent is class #32770, but not consistently.
If I call WaitChild for this same object it finds it all right. Also, I called WaitNamedChild in TestComplete directly, exact same parameters, and it worked.
I'm using connected application - C#, I tried the same in VB.net, just in case, but same result. It appears there is a problem only when using this with connected app.
Thanks.
