Will there be any alternative while interrogating the windows controls with long hierarchy?
While interrogating some controls using windows adapter we are getting a long hierarchy. As there is a risk involved in making all the controls unique in the hierarchy, Is there any way to mitigate this risk?
Naming is really up to you and your standards. I really wouldn't try to rename any controls that I am not specifically using as that would just require extra time. If you do want to name them, I would name them all after the parent and then the type of control they are followed by an ordinal number to make each unique.
When you have a large hierarchy, you need to make sure that each and every control in the hierarchy is matched properly and uniquely.