Hi,
Name mapping is used to simplify complex object structure of your application.
If you consider typical application most objects names and properties are not used to create test. (They need to have in application, but we testers not using) Also using name mapping we can make more comprehensive short names for testing purpose.
For eg: with name mapping some object like…………………..
“.Sys.Process("onelinkpromgn").Window("#32770", "ThinkPad OneLink Dock", 1).Window("Button", "Network and Sharing", 4)”
Could be mapped to shorter name like “NameMapping. Onelink.SharingBtn”
So if in your script you have used that short name, then without namemapping it cannot find what object you are referring to.
But there are people out there who don’t use namemapping. Either using exact names or using code to find necessary objects and properties.
In your case if you have used namemapping yes then you need it. To get rid you have to carefully remove all dependencies for name mapping in your script.
By the way why do want to get rid of?
What do you mean by NameChild?
What is tne VCL object?
Most ppl in this forum agrees
1) Do name mapping manually (if auto mapping used it will get complex )
2) Carefully select what objects should be mapped (eg only commonly used objects)
3) Keep mapping as simple as possible ( eg;- Map only objects high in hierarchy so you may use find(s) to get children )