Forum Discussion
If you decide to go through the process of removing NameMapping from your project, as NisHera mentioned, this is not simply a matter of removing the component from your project explorer.
You mention you are referecing "NamedChild"... I'm guessing you're using either WaitNamedChild or WaitAliasChild? If so, then those are dependant upon the objects actually being part of NameMapping... they will not work without NameMapping. These are the places where you will need to replace the reference to your object with something more native... you mention VCL...
So, where you might have it mapped as
Aliases.MyApp.MyForm.MyButton
To use it without NameMapping, you MIGHT need to go like
Sys.Process('myapp').VCLObject('myForm').VCLObject('myGroupPanel').VCLObject('myButtonGroup').VCLObject('OKButton')
Notice a couple of things:
1) The NameMapping has the advantage of being able to shorten and ignore intermediary items in the component tree. So, a short Alias string MIGHT need to be replaced with something much longer
2) Notice the button names... it is possible that these two things could represent the EXACT same component... but NameMapping allows you to assign your own naming convention to items without having to be limited to what is in the code.
Basically... if you remove NameMapping, you're looking at a total re-write of your test project.
I guess the next question is... Why do you want to remove NameMapping?
Hi All,
thanks for all your valuable inputs.
Kudos!
Related Content
- 11 years ago
- 2 years ago
- 4 years ago
- 4 years ago
- 6 years ago