Conversation
|
@mwhapples - would you be able to smoke test our update to JAB or suggest smoke testing steps? Here is a build to test with: |
|
I will give it testing today. |
|
As an aside, are you aware that (java 21 is out and that is supposed to be LTS, so would it be better to go to (java 21 JAB? |
|
Zulu isn't offering a 32bit build of 21 unfortunately, I'm not sure if 32bit support is fully dropped in that release or they just haven't made a build yet |
|
I see 32bit was deprecated in 21, probably why they didn't create a build |
|
As my projects using Java are only targetted for 64-bit systems, I didn't notice that X86 32-bit was deprecated in 21. I have looked around and seems like all the OpenJDK builds no longer include 32-bit (eg. adoptium, Azul, Microsoft, Amazon corretto, etc). |
|
Yesterday I tried the build and did not notice anything untoward, at least not compared with existing JAB support. However I was using it whilst working in PyCharm, so its more real world testing than methodical testing of different Java components. |
|
Thanks for the testing, it is appreciated |
Incorporates changes from nvaccess/javaAccessBridge32-bin#1 Update JAB to v17.0.9 from v13.0.1 Followed steps in the NVDA JAB README
|
@seanbudd Will it improve anything for the accessibility of existing java applications such as Android Studio? |
|
There are some Java Access bugs I am fairly sure which will not be affected by this change, unfortunately they would require API changes to the Java Access Bridge or for NVDA to do something more intelligent with what it gets. One such example would be notification/announcing expanding/collapsing treeview items. This is not to say there won't be any improvements, but I doubt they are going to be anything major. |
|
I will still give it some testing whilst using (java based applications. |
Updated the dll file following the README steps.
Smoke tested with PyCharm.
If there are known smoke testing steps, these should be added to the README.