Ranorex Forum

Thx for the tips, but this is unfortunatly not a solution.
When i try this "/form[@title='Ranorex test']?/?/listitem[@index='1']" Ranorex select element2, but when i add an element (element0 for example) at the top of the list, Ranorex select element1.
I need to use something like this : /form[@title='Ranorex test']/?/?/listitem[@text='element2'] but this is not correct.
Do u have any idea please ?

Hello yfrindel,

Well, if the index of your list elements changes you will need to find some attributes in order to identify your elements uniquely. Afterwards, they can be selected independently from their actual position within the list.

Regards,
Robert

hi,

Indeed i try to find the element by the text, but i don't find the text anywhere, except in the rawtext. How can i link the element and his rawtext ?

thx

What you can try is to get the RawText Row attribute, store it in variable and then use this variable in ListItem Index attribute. Like this... But I have no clue how reliable this solution might be with your "realworld" listbox? The order of ListItems may be different than order of RawTexts and so the above solution may not work.

And next problem, Ranorex seems does not return RawText for all windev list elements! For example, there is no Element4 rawtext returned from the example listbox you posted in your previous post. So the above solution may work with some elements, but most probably not all of them?

Indeed, i have not the same number of rawtext as listitem. that's strange.
On my mind, ranorex don't work very well with windev.
But I 'm still pleasantly surprised by the efficiency of ranorex

Hi,

You may still be able to increment/decrement the number obtained from RAWText via user code (before using the variable in Repository). Unfortunately, using RAWTexts (GDI approach in general) is always tricky and I would recommend to use it only in simple cases, like obtaining the button name. Element recognition via index numbers obtained from RAWText is always a bet

As for the Ranorex reliability with windev controls, I can only speculate that the problem is caused by the windev's lack of proper accessibility implementation? If the windev cotrol is not designed with the accessibility in mind, there is not much Ranorex folks can do about it. I think Ranorex folks can provide you with more technical details.