object recognition for delphi object is slow.

[Subbulakshmi]

Hi,

Our application is developed in Delphi. There is one frame, where I click on Save, one dialog box appears. Even if it is visible, Test Complete takes lot of time to click on OK button. I have added WndClass and WndCaption properties. Tried with FindChild as well. It takes same time only. 

[tristaanogre]

I'm assuming you're using NameMapping.  Is the Extended Find flag checked on any level of the mapped object tree leading up to that object?  Extended Find operates similar code to FindChild so the timing may be similar.

[Subbulakshmi]

Hi,

I tried checking Extended Find. It took the same time. 

[tristaanogre]

So... it was unchecked and now it's checked?  I kinda meant the opposite, that the flag may be checked.

Next question... I'm assuming that you're adding appropriate "wait" commands for the dialog?  It could be that the test is running faster than the application and so things are being attempted before the app is ready, causing confusion.

But, honestly... what we need is more detail.  Please post a screen shot of the Object Browser properties of the object that is taking too much time to be recognized.  Also, a screenshot of how it is Mapped in NameMapping would be helpful.

[Novari-QA]

I just had this isssue. I am glad someone else has as well.


Steps to fix or at least for me:
Right Click Name Mapping

Open Source File Location

Copy the NameMapping file.

Paste File onto your Desktop

Delete All of your Objects in your name mapping tree... all but the Sys Object

Right Click Name Mapping and use the option "Merge With"
Select the file you put on your Desktop.

Bam everything is fast again.

[tristaanogre]

That's interesting... it could be that the NameMapping file gets corrupted in some way after a large number of edits.  

Question: Are you using the NameMapping images?  We're not and we're not seeing major slow down in our object recognition.  Could be an effect of the NameMapping images. Would be interesting to find out.

[Subbulakshmi]

Hi,

This solution is not working for me. 

[Subbulakshmi]

Hi,

It was checked earlier and now I have unchecked. It takes the same time as always. Please find screenshot for name mapping attached. 

[Subbulakshmi]

Hi,

We are not using images. 

[shankar_r]

In order to identify where the slowness is getting started, try below steps.

Just try from parent like below,

Sys.HighLightObject(NameMapping.Sys.LandmarkII);

Sys.HighLightObject(NameMapping.Sys.LandmarkII.TLMKMessage);

If you find the slowness in 1st line then you want to give unique properties to the get object quickly. if you have similar objects it may take time to  select the object based upon your properties.