Forum Discussion

Contributor

9 years ago

Is there a way to turn off object recognition hint in TestComplete12?

Hello, We just updated to TestComplete12 and after our lab run we noticed we had about a dozen of our tests start spitting out warnings for "Object Recognition Hints". These tests were not failin...

wcach
9 years ago
Hello,

We haven't found an option to turn off this new feature.
If this helps, we are blocking the warning via the Events/GeneralEvents/OnLogWarning:

Sub GeneralEvents_OnLogWarning(Sender, LogParams)
' Block the warning "An object recognition hint" from TC12
If LogParams.MessageText = "An object recognition hint. See Additional Information for details." Then
LogParams.Locked = True
End If
End Sub

Regards

wcach

New Contributor

Hello,

We haven't found an option to turn off this new feature.

If this helps, we are blocking the warning via the Events/GeneralEvents/OnLogWarning:

Sub GeneralEvents_OnLogWarning(Sender, LogParams)

' Block the warning "An object recognition hint" from TC12

If LogParams.MessageText = "An object recognition hint. See Additional Information for details." Then

LogParams.Locked = True

End If

End Sub

Regards

tristaanogre

Esteemed Contributor

9 years ago

If this is the code you are using, or something similar...

if Aliases.Device.pnlBack.WaitProperty("Exists", True, 1000) = true then
   call Aliases.Device.pnlBack.Touch
   delay(2000)
end if

Then the problem is actually pretty simple to solve. You cannot call the "WaitProperty" method on an object that does not exist. If there is no object, you can't call a method on the object.

What you need to do is use WaitAliasChild. Change your code to

if (Aliases.Device.WaitAliasChild("pnlBack", 10000).Exists) then
   call Aliases.Device.pnlBack.Touch
   delay(2000)
end if

That SHOULD correct your object recognition problem.

WaitProperty should only be used if you know the object exists and for detecting changes in a property value, not changes in the existance of an object.

AlexKaras
Champion Level 3
9 years ago
Robert's reply (https://community.smartbear.com/t5/Desktop-Testing/Is-there-a-way-to-turn-off-object-recognition-hint-in/m-p/127430#M7297) is the correct explanation of the reason of the problem and how it should be avoided.
- lleppert
  Contributor
  9 years ago
  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.
  
  Thanks all.
  - tristaanogre
    Esteemed Contributor
    9 years ago
    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.
larolsen
Contributor
9 years ago
Hi Robert

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 :-)

/Lars