Forum Discussion
tristaanogre
13 years agoEsteemed Contributor
Perhaps I was unclear:
I was suggesting that you change to start using the native NameMapping. This will, as stated, perform those tests you are looking for along the whole tree without having to individually do the checks.
The only other suggestion I have is to write "smart" code. For example, if you perform an action, that will close one window and open another, you don't need to check for the process or for the parents of those windows, you just need to check and makes sure the one window closed and the next one opened. While your application has a deep hierarchy, you may not need to test all along the hierarchal tree, only those items that you know change from action to action.
I was suggesting that you change to start using the native NameMapping. This will, as stated, perform those tests you are looking for along the whole tree without having to individually do the checks.
The only other suggestion I have is to write "smart" code. For example, if you perform an action, that will close one window and open another, you don't need to check for the process or for the parents of those windows, you just need to check and makes sure the one window closed and the next one opened. While your application has a deep hierarchy, you may not need to test all along the hierarchal tree, only those items that you know change from action to action.
Related Content
- 14 years ago
- 6 years ago
- 10 years ago
Recent Discussions
- 5 days ago
- 5 days ago