win_get_text: looking for advice re: best practise
A couple of questions:
1) When defining the search area with the cursor, is there any advantage in making the area as large as possible (or just big enough to get the text)? I was thinking that the bigger the area, the less sensitive the script is to those values moving slightly. Then again if you make it big and something else gets placed in that area that could cause problems as well. I guess it's swings and roundabouts. What does everyone else do? Am I thinking too much? Do I need to get out more? lol
2) In situations where I'm reading multiple values and winrunner writes \r\n (I presume) characters between the captured values, is there any advantage (e.g. improved reliability) in splitting the win_get_text output before utilising it (even though in my case I don't need to - I'm doing two win_get_text commands and just want to compare the two sets of output).
All input appreciated.
Re: win_get_text: looking for advice re: best practise
I prefer to make the it as close as possible to the actual text I'm trying to grab for maintainability issues and reliability. Both points you made are valid...this is just my practice.