Julia
That's not the case here. At one point, I could select 2 different toolbars in Namemapping, each having different index values, and TC would highlight the same toolbar in my app (there's no way the same toolbar could have an index of 1 and 3 at the same time). Unfortunately, using index values has been the most reliable way to identify objects in my app. I use required children when possible to increase the reliability, but it's not always available. I'm working with a custom Eclipse RCP app, which is a challenge due to all the extra composite objects that Eclipse generates.
Since upgrading to 8.7, Namemapping just doesn't seem as reliable. I have the problem above. It also doesn't always existing object that have already been mapped. When working with a new window or screen, I like to map all the objects so that when I record, it will use meaningful names (txtName instead of Text1). I have found with 8.7, it just ignores what I have already mapped and creates brand new window and objects.
Last week, I had an issue where I had two objects with the same name mapped but located on different branches. TC kept getting them mixed up. For examples,
Window1 | Group1 | txtAddress
Window1 | Group2 | txtAddress
Window1 | Group1 | txtAddress is the active window, and my test correctly used it until it hit an error. The error then reports that it couldn't find Window1 | Group2 | txtAddress, which was never a part of the test. I had to delete both objects and remap to move on.
