Hi All,
This issue was resolved when we uncheck * option in List of accepted windows MSAA option(Current project properties).
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.
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.
Hi,
We are not using images.
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.
Hi,
This solution is not working for me.
