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
include a list of supported UIA patterns into the developer info #5712
Comments
Hi, Could you attach the plug-in as a zip file so someone can code review it? Note that UIA patterns wil work well for UIA objects (there are broken UIA objects, so be careful with those). Thanks. From: dave090679 [mailto:notifications@github.com] hi guys, inspired by the jaws touch cursor's object properies dialog, I wrote some code to generate a list of supported UIA patterns for the current navigator object IMHO it would make sense to include such a patterns list into the developer info generated by nvda+f1 To use my global plugin, press nvda+shift+f1 If the navigator is placed on a uia object, the patterns list is displayed as a flash message and it's also written to the nvda log (as an info istring) If the navigator isn't placed onto a uia object, an error message is displayed I've tested the global plugin with various (non)UIA objects in Windows 7 x64 as well as in Kaspersky Internet Security 2016 You can get the global plugin from my dropbox: https://dldropboxusercontentcom/u/67471/uia_patternspy happy testing Dave — |
hi all, This is a first try attaching my code as a blank .py file. I tried this happy testing Dave import ui |
hi all,
this is a second try to attach the code as a 7zip compressed zip file.
When I try to do this using the website, it says that it "cannot process
the file".
happy testing
Dave
|
Simply rename the .py to .py.txt and it should work. On 1/27/2016 12:21 AM, dave090679 wrote:
Websites: email me at derek.riemer@colorado.edu mailto:derek.riemer@colorado.edu |
Hi Drek, Here comes a third (and I hope final) Try to attach a file. This time, happy testing Dave import ui |
I came across this and really find this interesting. @michaelDCurran, @dkager, @josephsl: What do you think? If you agree with the approach used here, I'd be happy to create a pr with this functionality integrated into the developer info. |
Hi, don’t forget to keep this info updated with new Windows 10 releases. Thanks.
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Friday, February 9, 2018 12:34 PM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] include a list of supported UIA patterns into the developer info (#5712)
I came across this and really find this interesting. @michaelDCurran <https://github.com/michaeldcurran> , @dkager <https://github.com/dkager> , @josephsl <https://github.com/josephsl> : What do you think? If you agree with the approach used here, I'd be happy to create a pr with this functionality integrated into the developer info.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#5712 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkJTcPkOtTIonW0i31ThYMRVw62hpks5tTKurgaJpZM4HMXyu> .
|
I'd like to have an implementation based on the AutoProperty getters that are available on an object.
|
Here is a branch that adds the available patterns to the developer info: @josephsl: Would you like to take a first look at it? This implementation should be future proof, I'm not sure whether it is past proof though. For example, I'm not sure what _prefetchUIACacheForPropertyIDs does with property ids that are unavailable on a system. May be its just a piece of obtimisation that is not necessary at all. |
Hi, one way to test if it works in the past iterations is testing under Windows 7 SP1 and 8.1. Thanks.
From: Leonard de Ruijter [mailto:notifications@github.com]
Sent: Saturday, February 10, 2018 4:29 AM
To: nvaccess/nvda <nvda@noreply.github.com>
Cc: Joseph Lee <joseph.lee22590@gmail.com>; Mention <mention@noreply.github.com>
Subject: Re: [nvaccess/nvda] include a list of supported UIA patterns into the developer info (#5712)
Here is a branch that adds the available patterns to the developer info:
https://github.com/BabbageCom/nvda/tree/availableUIAPatterns
@josephsl <https://github.com/josephsl> : Would you like to take a first look at it? This implementation should be future proof, I'm not sure whether it is past proof though. For example, I'm not sure what _prefetchUIACacheForPropertyIDs does with property ids that are unavailable on a system. May be its just a piece of obtimisation that is not necessary at all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#5712 (comment)> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AHgLkHSEDxes24ec7hnjJZviIA3AHCWQks5tTYujgaJpZM4HMXyu> .
|
Hi, Testing shows it won't work on versions earlier than Windows 10, as some UIA patterns were introduced in later Windows releases. One way to get around this is to wrap the appendProperty function (line 715) with a try/except block that catches COMError and skip over that when this happens. Thanks. |
This should have been fixed. I will try this on Win7 later today.
|
hi guys,
inspired by the jaws touch cursor's object properies dialog, I wrote some code to generate a list of supported UIA patterns for the current navigator object. IMHO it would make sense to include such a patterns list into the developer info generated by nvda+f1.
To use my global plugin, press nvda+shift+f1. If the navigator is placed on a uia object, the patterns list is displayed as a flash message and it's also written to the nvda log (as an info istring). If the navigator isn't placed onto a uia object, an error message is displayed.
I've tested the global plugin with various (non)UIA objects in Windows 7 x64 as well as in Kaspersky Internet Security 2016.
You can get the global plugin from my dropbox: https://dl.dropboxusercontent.com/u/67471/uia_patterns.py
happy testing
Dave
The text was updated successfully, but these errors were encountered: