Thank you Robert and Alex.
Unfortunately, I am not using the WaitProperty method where I am experiencing the object recognition hint. I am calling FindChild.
However, that does look like it will help Lars and possibly Orvai. I have accepted wcach's solution as it was exactly what I was looking for.
FindChild should return the empty stub that WaitAliasChild does if it cannot find the object. It should then have an option for checking the "Exists" property. Even with FindChild, you still want to make sure you test for Exists before you attempt to use it. So, it would be something like
MyFoundObject := Aliases.MyRootObj.FindChild(MyPropertyNameArray, MyPropertyValueArray, 0, true); If MyFoundObject.Exists then begin DoMyStuff; end;
Attempting to use MyFoundObject before you verify it actually exists will result in the hints and warnings you're experiencing.
My code is checking to make sure the object exists before using it. In fact, there is no issue in actually using the object. The object is found and utilized without error after the object recognition hint is thrown. That is why I simply want to ignore the hint, because otherwise the test runs green without issue as it did before this new feature.
Thanks for your input.
Thanks for the input, and I will have this in mind when I write new code. BUT, this way of waiting for a property on an alias did not cause problems for us before the release of TC12.
But the code you suggested is definitely cleaner and "more" correct, thanks :-)
So this is a nice suggestion from wcach to keep the stuff out of the log file, but I'm still waiting the five minutes for TestComplete replay to get past the object recognition hint nonsense.
Worse is that in my case TestComplete has already clicked the button it's busy hunting for and the window that button was on has been closed (because that's what the button does)!
Is there ANY way to actually shut off the Hinting? Not logging the warning doesn't help if it still waits the five minutes hunting for the missing buttons.
Yes.... map your objects better.
Honestly, it comes down to doing a better job of selecting identification properties for your mapped object so it doesn't give the hints and warnings. It means investigation and a bit of elbow grease to find a better way of identifying your object. I'm guessing that you're using Extended Find in your name mapping... you might need to add additional hierarchy into your NameMapping to drill down closer to the object.
tristaanogre - please go read that message before yours again.
TestComplete clicked the button and THEN starts the process of hunting for the button in the window that's been closed.
This is not a Community Hero type of response: "Yes.... map your objects better."
Can you post here a relevant piece of code that illustrates the problem?
Preferably, with the code lines where the reference(s) to the problematic object(s) is/are obtained?