Page 1 of 1

Recognition of Custom Elements Android

Posted: Fri Oct 24, 2014 11:13 am
by lucian.teodorescu
[Support Team: Moved to new topic]

I have an update on this post:

I am trying to identify some elements inside a android element (in fact is a screenblock displayed as matrix). I have tried a validation during recording, then a better path with Ranorex Spy. Everything failed.
There you can see the path through the container. The "text" element was found through validation, but there are many other elements like this. They are not indexed and the other attributes are the same.
I could not managed to link the textbox with the text on the left because the last is not accessible (I didn't try imaging validation since the list of the elements is dynamically generated).

Could you help me to find a good path for all those elements from inside the container?

Thank you,
Lucian

Re: Recognition of Custom Elements Android

Posted: Mon Oct 27, 2014 12:49 pm
by Support Team
Hello Lucian,

Do you always get just the “Text ‘19’” element within the screenblock container or are there other text elements as well? (I cannot see any within your Ranorex snapshot). If yes, please try to create another snapshot of the application which depicts all other elements as well.

Thanks,
Robert

Re: Recognition of Custom Elements Android

Posted: Tue Oct 28, 2014 8:25 am
by lucian.teodorescu
Hi Robert,

Another more detailed snapshot of the screen blocks, I send it to you via e-mail (to [email protected]) because I cannot post it on forum.
More details that I found: I never get to that level in the forms-tree by Ranorex Spy alone. To get this snapshot I had to record the actions that led me to this screen block. Then from all the text elements inside the screenblock, only the last one visited on each column is available. In snapshot you will find that “Text 5” is invisible (and was the last edited on that column) and “Text 3” is visible on the second column. If I move to let’s say “Text 10”, the same repository element will be used and I will no longer see “Text 5” while the “Text 3” will be invisible.

Also it’s very strange that I cannot find the text from the very left of the container (I have another screenblock similar to this one, but it has check boxes instead of text elements: I face the same difficulties to verify what checkboxes are checked or not).

Many thanks for your help.
Lucian

Re: Recognition of Custom Elements Android

Posted: Thu Oct 30, 2014 2:49 pm
by Support Team
Hello,

As already discussed via email:
We do not have enough information about the accessibility implementation of your custom controls. The standard controls are supported and can be recognized.

Regards,
Robert