Inputs are not detectable by Ranorex

Ranorex Spy, Recorder, and Studio.
yassine
Posts: 11
Joined: Mon Jan 09, 2017 12:49 pm

Inputs are not detectable by Ranorex

Post by yassine » Fri Jan 20, 2017 9:58 am

Hello every one,

I need to detect some inputs that are not detectable by default by ranorex.

By default, table controls and inputs were not detectable by Ranorex Spy, I tried to add the class Name and process name of inputs and tables to GDI capture list, It worked for table control and table's cells became detectable by the spy, but unfortunately It did not work for inputs.

Is there any special configuration that I have to add so my inputs became detectable.

In attached files, you can find an exemple (screenshot and snapshot)
Attachments
Filtres_Screenshot.png
Filtres_Screenshot.png (34.05 KiB) Viewed 540 times
filtres.rxsnp
(1001.1 KiB) Downloaded 40 times

User avatar
odklizec
Ranorex Guru
Ranorex Guru
Posts: 3930
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Inputs are not detectable by Ranorex

Post by odklizec » Fri Jan 20, 2017 1:01 pm

Sadly, it looks as if these "magicsoftware" GUI controls used in your AUT, were implemented without proper accessibility support? What you can try is to track the problematic elements with MS Inspect (as discussed here) tool. If Inspect can "see" these controls, then it may be a Ranorex issue, which could be corrected by Ranorex folks. If Inspect cannot see them as well, it's definitely a problem of these controls.
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration