Forum Discussion
brentpaine
13 years agoOccasional Contributor
Hi Tanya,
Actually I wanted to be able to collect the information in order to perform localization testing. So I actually have a spreadsheet that I work against for all of my translation strings, so I wanted to collect all of the text properties of any elements on the screen and then compare those against my spreadsheet and then I could switch the language for the app and compare my localization strings.
Anyway, I think I was overthinking it. In the end, I simply used FindAllChildren with a deep search depth and pulled out the name and text, so I could identify the object by name and then have some sort of text that is currently associated with it. Then I can create a lookup table and run my comparisons that way.
Thanks for the response though.
Brent
Actually I wanted to be able to collect the information in order to perform localization testing. So I actually have a spreadsheet that I work against for all of my translation strings, so I wanted to collect all of the text properties of any elements on the screen and then compare those against my spreadsheet and then I could switch the language for the app and compare my localization strings.
Anyway, I think I was overthinking it. In the end, I simply used FindAllChildren with a deep search depth and pulled out the name and text, so I could identify the object by name and then have some sort of text that is currently associated with it. Then I can create a lookup table and run my comparisons that way.
Thanks for the response though.
Brent