Object Identification in Qt 5.15.0 seems broken

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
Martin Hanysz
Posts: 1
Joined: Thu Jul 09, 2020 1:45 pm

Object Identification in Qt 5.15.0 seems broken

Post by Martin Hanysz » Thu Jul 09, 2020 2:12 pm


My company develops a windows application based on Qt. We recently updated from Qt 5.12.7 to the latest Qt release 5.15.0 and ranorex's object identification seems broken since then.

All objects are missing the Qt specific attributes and some objects are not detected at all. In addition, the objects that are detected, appear twice in the spy, once with the attributes for General, Layout and Accessible and once with the attributes for General, Layout, UIAutomation and UIAutomationValue.

I attached two ranorex snapshots of the same dialog of the application. Apart from the Qt update, the dialog did not change. It has some text and only one button. With Qt 5.15.0, the text isn't detected at all and the button is detected twice, as described above. With Qt 5.12.7, all Qt elements that are used to divide the dialog into different sections are also detected. The text on the page shows up as two separate elements, one for each paragraph and the button also only shows up once.
(107.15 KiB) Downloaded 4 times
This behavior can also be reproduced using the Qt sample app from this thread https://www.ranorex.com/forum/spy-does- ... 15745.html. Once the Qt dlls are replaced with the ones from Qt 5.15.0, the described behavior can be observed.

1) Do you know if and how we can get the old object identification back?
2) Do you have experience with the combination of ranorex and Qt 5.15.0? Maybe there are settings we need to change in ranorex or our application that we overlooked?

Kind regards,
Martin Hanysz

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

Re: Object Identification in Qt 5.15.0 seems broken

Post by odklizec » Fri Jul 10, 2020 12:41 pm


It looks like a problem with Ranorex implementation of QT? It's most probably not optimized for Qt 5.15.0 yet? I would suggest to create a support ticket here:
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