QT5 app #1352
Replies: 5 comments
-
Hi, I am not familiar with how Squish identifies and parses Qt gui elements. However, So, I think that |
Beta Was this translation helpful? Give feedback.
-
Squish most probably use DLL injection approach for QML apps. We can create similar "qml" backend for pywinauto, but it requires pretty much work. Similar approach is already implemented for WPF apps (in pull requests at the moment). If somebody can help with it, I can advice where to dig. |
Beta Was this translation helpful? Give feedback.
-
I'm planning to tidy up current activities during New Year holidays and post the DLL injection package to PyPI ("injected" repo in the organization). Then I can merge WPF backend with DLL injection, and we can continue in similar directions. |
Beta Was this translation helpful? Give feedback.
-
See also #1353. Maybe it is possible to join efforts. |
Beta Was this translation helpful? Give feedback.
-
Yes, I think it is the same issue here. |
Beta Was this translation helpful? Give feedback.
-
Hi, first of all great job on this project.
I'm trying to make a POC for a testing project and this library is one candidate.
Internally we are using a dedicated platform for testing a QT5 application(Squish from Froglogic now Qt).
I did some comparison between Squish and pywinauto and there are some difference between how elements are identified.
I don't understand why we are not able to see more information in the app as Squish sees, the same is happening with Inspect.exe
Basically the pywinauto see what we see in Inspect.exe but Squish see more.
It identify elements and buttons with more information as text color, font name, images are identified with path ../...svg and some buttons that pywinauto that are identified with no name or auto_id in Squish we have a full name. If a button has a icon (for example close button has a X icon, in Squish we see also the button icon as child).
Any idea why?
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions