-
Notifications
You must be signed in to change notification settings - Fork 671
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Subscribe Events #1069
Comments
Hi @LexiconCode some prototype of script recorder was implemented for "uia" backend in PR #701. We postponed its productization as it is very complicated. The plan looks so:
We also hope to add macOS support soon as normal "ax" backend. Monitoring/recording capabilities on macOS are also possible, but it's a very long term plans probably. It depends on real demand and interest from my students. |
UIA recorder feature is tracked in #332. Also issues with label "New Feature" might be interesting: https://github.com/pywinauto/pywinauto/issues?q=is%3Aopen+is%3Aissue+label%3A%22New+Feature%22 |
Thank you for the information!
I made an attempt and it looks very complex to rebase. Due to the age of the PR it's hard to distinguish between its changes without having a deep knowledge of the upstream CodeBase. |
Yes, it's really bloody merge. :) If you really want to learn this code deeply, I can do this rebase in May. The feature itself is also not easy, but code changes look not so scary. Maybe this code can be re-used for nice notification handlers implementation (without fully functional recorder yet). |
That would be very generous of you and I would appreciate it. It gives a good place to start.
After looking over the code this is what I was going to suggest breaking it out into 2 separate PRs. The 1st focusing on Events to which the recorder could be built off it a later time. So your idea for notification handlers would seem to be a good direction. FYI: UI Automation is backwards-compatible with IAccessible2 as of the May 2019 Windows 10 update sources It may be helpful for your students to see the UI out of a framework in another context that in a similar domain. nvda screenreader is an interesting utilization of Microsoft UI automation framework. The code is well commented and highlights some of the challenges particular applications have utilizing accessibility APIs. My goal is to facilitate the speech recognition community. The SR community is looking for a deeper way to integrate with applications beyond emulating keys/mouse. The purpose being to provide hierarchy of methods to enhance accessibility of software. The goal in pywinauto is the to contribute back rather than re-implementing accessibility APIs ourselves. That way everybody benefits everyone. Some previous work on accessibility from the community. |
Luckily rebase for UIA recorder wasn't so hard. This branch contains UIA recorder rebased from |
Greetings most accessibility API framework have their own version of subscribing/monitoring events.
pywinauto is tooled towards UI automation (UI testing) not as an accessibility (screen readers/voice control) library. These cases are very similar but have a different focus.
I will not be able to do this alone but I would like to begin looking at what it would take to implement it within pywinauto. Any thoughts on this would be appreciated.
The text was updated successfully, but these errors were encountered: