Forum Discussion
Ooops.
I accepted the reply ... but doesn't solve my problem. Sorry!
Anyway .... I have no idea why the mapped name is not populated?
If I look at an object in the object browser, the "Mapped Name" field is blank. (It is blank for all objects as far as I can tell)
If I then look at the same object in my name map, and tell it to highlight on screen, it works correctly. They also work perfectly in the scripts that use them. I do not have "Find anywhere in the object tree" enabled. They are pretty specific mappings.
So the object is clearly mapped and working correctly.
So I don't know what is breaking the link between the two?
My previous project did not use a large name map file so it didn't cause any problems and I probably never even noticed this problem. My new one uses a much bigger name map file and I'm finding it more and more awkward to use as object mapping behaviour can be a little strange sometimes. I'm careful about the properties I use to map. I have to be. They have to remain cross browser compliant and parts of the tree can be difficult due to dynamic properties. I get round this using multi-part identification properties, wildcards and required child objects.
Either way, the mapped objects work just fine. But links to them from the object spy and object browser don't .....
I accepted the reply ... but doesn't solve my problem. Sorry!
Anyway .... I have no idea why the mapped name is not populated?
If I look at an object in the object browser, the "Mapped Name" field is blank. (It is blank for all objects as far as I can tell)
If I then look at the same object in my name map, and tell it to highlight on screen, it works correctly. They also work perfectly in the scripts that use them. I do not have "Find anywhere in the object tree" enabled. They are pretty specific mappings.
So the object is clearly mapped and working correctly.
So I don't know what is breaking the link between the two?
My previous project did not use a large name map file so it didn't cause any problems and I probably never even noticed this problem. My new one uses a much bigger name map file and I'm finding it more and more awkward to use as object mapping behaviour can be a little strange sometimes. I'm careful about the properties I use to map. I have to be. They have to remain cross browser compliant and parts of the tree can be difficult due to dynamic properties. I get round this using multi-part identification properties, wildcards and required child objects.
Either way, the mapped objects work just fine. But links to them from the object spy and object browser don't .....
Related Content
Recent Discussions
- 21 minutes ago
- 3 hours ago
- 4 hours ago