Hi,
If I got your question and problem right...
.FindChild() should work for you and it looks like you are using it correctly: call for .FindChild() and then check .Exists for the search result.
It is something else that makes me doubting:
> same name and location in the structure if it is on the page (browser->form->panel->LoadPanel Table)
I guess (as I don't know the exact implementation in the tested application) that despite the fact that the location and the name of the loading panel is the same, it is created and recreated by some page script when the page and/or page's data is reloaded. If the above guess is correct, then you should not keep the reference for the loading panel object in the variable, but must get the reference a-new every time. (Performance penalty should be minimal as the search is done by the sought for object's name.) Especially, considering the fact that you are using Aliases as the search root.
The reason for above is that the stored reference to the object uses explicit path to it (e.g. Aliases.browser.Form.Panel.LoadingPanelTable) and if the LoadingPanelTable object is recreated during page/data reload, then the stored referenced object is invalidated and thus TestComplete fails to find the old LoadingPanelTable object even if the new created one has the same name and position in the objects tree.
https://support.smartbear.com/testcomplete/docs/testing-with/object-identification/name-mapping/how-to/refresh-cache.html might provide additional useful info.
.FindChild() should work for you and it looks like you are using it correctly: call for .FindChild() and then check .Exists for the search result.
In theory, yes, but I'm getting an object does not exist error if it's not on the page at all
The reason for above is that the stored reference to the object uses explicit path to it (e.g. Aliases.browser.Form.Panel.LoadingPanelTable) and if the LoadingPanelTable object is recreated during page/data reload, then the stored referenced object is invalidated and thus TestComplete fails to find the old LoadingPanelTable object even if the new created one has the same name and position in the objects tree.;
Valid point. It's been working fine so far, but I should probably change it
I'm getting an object does not exist error if it's not on the page at all
Can you provide a relevant line of code and exact error message from test log, including the text from the Additional Info pane?
My apologies. That was old data - I was having the issue on Friday before a minor code change last thing in the day that fixed it and I forgot about it over the weekend doh ! :smileysad:. Today I have it working, but I'm still hoping to find a way of making it a bit more efficient. My Run Timeout is currently 30 seconds (yes, some controls on my site actually take that long), so this function could take 30 seconds plus change before it continues. On a page with just 4 controls, that could add 2 minutes. I am using a FindChildEx though - that cuts it down. I could do:
var currentTimeout = Options.Run.Timeout; Options.Run.Timeout = 100; // find table, wait etc. Options.Run.Timeout = currentTimeout
But that opens the window again for the table actually being there, but the timeout being too short for TC to track it down because the page loads a bit slow. I'm not saying there's a better solution than the current one I have. It would just be nice to ask TC to just tell me if it's on the page as quick as possible rather than try and find it for a long time that I make up and tweak every time the test doesn't find the table even though it's there all because I made the delay too short.
It would just be nice to ask TC to just tell me if it's on the page as quick as possible
The general sequence is like this:
-- If the click on some web element can reload page/page data (as opposed to just displaying/hiding something on the page via script), then page.Wait() must be executed. .Wait() method of the page object waits until the web page source is obtained from web server and the browser completes initial page processing;
-- If the page contains elements that are downloaded from web server via additional requests (Ajax) and you either need to interact with these elements or web page is not responsive until these elements ere obtained, then you must execute page.<container>.WaitChildEx() with the long enough timeout to delay until the elements are obtained. (Note, it is safe to set very long timeouts here because .WaitXXX() methods return as soon as the sought for object is obtained. The only case when too long timeout might be not reasonable is when it is OK for the sought for object to be absent on the page. In this case you must find a good enough timeout value to wait long enough for the object but not wait too long.)
-- Optionally, depending on the implementation of the tested application, you may need to additionally wait for the found object become visible on the page. (It may be required to check different indicators to ensure element's visibility: from .Visible property in the simplest case to the values of class/width/height properties of the element itself or including a set of its parents.)
-- One more additional delay might be required if the data for the target web element are also obtained via separate request. If this is the case, then you must figure out criteria that are met when the element is populated with data and delay appropriately;
-- It is usually safe to proceed with the test actions after all above actions are done.
