Forum Discussion
So, start looking at your component mappings. Make sure that the components you're trying to work with haven't had property changes.
Use Object Spy on the components in question to investigate what properties are present and their values and compare those to your mapping. It's possible that the problem is not with TestComplete but with the application, that something changed.
If it is a problem with component mappings, then how my code is executed and object on screen in not highlighted. I have checked in the same way using object spy and compare them with the mapping items.
No difference is there. No change is there in my application, even in login page I am getting this issue.
Any plug-ins need to install or any other thing need to update or what , I am not getting.
Regards,
Veena.
- tristaanogre6 years agoEsteemed Contributor
OK, so the code is executing just fine? That's a different story entirely.
Do you get any error messages or anything when selecting "Highlight on screen" from the context menu in NameMapping or your workspace?- VNA6 years agoOccasional Contributor
- tristaanogre6 years agoEsteemed Contributor
There could be many reasons for that message. I get it all the time when I attempt to highlight an object that doesn't have a visual rendering on screen (Visible is set to false, for example) or, in some way, it is not a visual component.
Basically, if you can't see it on screen, chances are you cannot highlight it. You may still be able to see it in the object browser (context menu has option "View in object browser") where you can see what might be preventing the highlighting (visible is false, it's hidden, height and width are both 0, etc).
So... my suspicion is that it's not necessarily a problem with 12.50 but perhaps a context thing... that, in a specific situation, you may not be able to highlight something on screen.
Related Content
- 2 years agopatricialopes
- 9 months agoLuukdb
- 4 years agoPUM-Prodat-SQL
Recent Discussions
- 21 hours agovladd1