Hi rraghvani,
Yes, I have tried WaitChild method, but no luck. The only thing that is working everytime is when I restart the application I am working with.
Champion Level 3If you use the Object Browser (not Object Spy), is there any indication as to when the child object is created?
Are you able to post a picture of the Object Browser, before and after object is created (similar to my example)?
I am posting a screenshot of the Object Browser, the highlighted object is what I am trying to click:
This object is always visible physically, as you can see in the screenshot the object is visible but still the Height and Width is 0. I am also including the screenshot of the object browser after restarting the application, where Height and Width is not 0 and I am able to click the object:
Champion Level 3Notice also the ControlIndex and ControlIndexGroup are "-1". It looks like the UI element is being destroyed and never properly recreated, or Memory corruption or rendering issues.
What happens when you try code refresh, or Object Browser panel GUI refresh
Sys.Refresh(); // Refresh process list
Sys.Process("MyApp").Refresh(); // Refresh UI tree inside app
I tried using Sys.Process("AXISEL").Refresh(); in my code, in my first attempt when I run the test case I get the same error as I reported. I tried putting a Delay upto 25000 milliseconds but no luck. In my second attempt it always work, not sure about this behavior.
Champion Level 3Are you able to include the before and after screenshots of the UI as well, together with the Object Browser?
In the Object Browser, if you click "View more members (Advanced view), you will get more properties and methods exposed. There may be other properties/methods that will give you an indication as to when the UI can be interacted with. Also, ask your Developers, they may be able to help too.
Hi rraghvani,
I am posting the screenshot of the UI, the object "TestComplete Work Area 1" is always visible, so there's no change in UI when the height and width is 0 vs when it's not 0.