I am having to spy a window in UI mode since it will not spy in any other mode. My problem is that the only dependable attribute to zero in on is the "match index" field. It works as long as the window looks exactly the same each time (same number of fields present); however, if a particular page is displayed where one of the fields above my match index is null then all of sudden my "read" command doesn't grab the right field.
For instance:
1. I'm looking for a text field that most of the time winds up being match index = 55
2. The problem is that any field of match index 1 - 54 could possibly be null...I never know which one could be null
3. When this occurs then suddenly to get the text field referenced in #1 above it is now a different match index
4. I do not know how to get around this issue and was wondering if anyone had experience of resolving this problem
For instance:
1. I'm looking for a text field that most of the time winds up being match index = 55
2. The problem is that any field of match index 1 - 54 could possibly be null...I never know which one could be null
3. When this occurs then suddenly to get the text field referenced in #1 above it is now a different match index
4. I do not know how to get around this issue and was wondering if anyone had experience of resolving this problem