Skip to content
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

Starting NVDA after a Java application requires a restart of the app for NVDA to read the interface #10296

Closed
snufas opened this issue Sep 28, 2019 · 8 comments · Fixed by #10526
Milestone

Comments

@snufas
Copy link

snufas commented Sep 28, 2019

NVDA problem with java applications
hello dear fellow programmers and users of NVDA, I am noticing a problem for a while now regarding NVDA usability with Java applications. Most of us probably know that java access bridge has to be enabled for it to work and it does, however there is a problem with accessing the interface when NVDA is restarted and application is still on. The problem is that the application is no longer accessible and NVDA does not pronounce anything on the window unless I restart the application I am working with. To conclude, basically if I turn off NVDA while am working with the Java application I have to restart the application for NVDA to read the GUI.
I tested same with Jaws and a problem does not exist. I'm writing this now because I never saw this problem being addressed before and this problem exists for very long time. I don't know myself where the problem could be, but I know for a fact that this problem affects any Java application.
So I am wondering now whether this issue can be addressed in future NVDA releases? Our developers aware of this issue? If yes why it is not fixed yet? I am thinking theoretically, if jaws does not have that issue it is possible to theoretically fix the problem.

A quick note how come NVDA does not have the feature where mouse is moving based on location that NVDA has focus on? The reason I am asking this is that I encountered many situations whereNVDA does not read the application, when using keyboard on its own, however when I hover the mouse over different elements of the application it works without any problems. I know that NVDA has a feature " move navigation object to mouse " it would be nice however to have the mode whereby it does that automatically is extremely handy in the situations where regular cursor doesn't work.

Thank you for reading and I hope some of my feature requests can be addressed in the future.

Steps to reproduce:

Turn on any Java application and restart and NVDA while the application is on

Actual behavior:

The NVDA is silent and does not pronounce any elements on the screen.

Expected behavior:

theoretically it should work as if I started the java application while NVDA is on.

System configuration

NVDA version 2019.2 installed on my pc.
Using Windows version 10.0.17763 workstation

@Brian1Gaff
Copy link

Brian1Gaff commented Sep 29, 2019

@leonardder
Copy link
Collaborator

leonardder commented Sep 30, 2019

I always thought this was a limitation in Java, did not know that JAWS doesn't have this issue. I agree that it is slightly annoying to require restarting the app.

I will try to have a short look into this in the near future.

@leonardder leonardder self-assigned this Sep 30, 2019
@leonardder leonardder changed the title NVDA problem with java applications Starting NVDA after a Java application requires a restart of the app for NVDA to read the interface Sep 30, 2019
@snufas
Copy link
Author

snufas commented Sep 30, 2019

@leonardder
Copy link
Collaborator

leonardder commented Oct 3, 2019

Quick investigation reveals that the isJavaWindow function on the access bridge DLL returns False on the window of the application, even though it is a Java window. This is pretty strange.

@leonardder
Copy link
Collaborator

leonardder commented Oct 3, 2019

One possibility would be changing JABHandler.isJavaWindow to return True when the access bridge is available and the window class is SunAwtFrame. I think in these cases, even though we may yield the JABWindow class in possibly faulty cases, kwargsFromSuper should still report False.

@michaelDCurran: May I have your onion here before filing a pr with the suggested change?

@michaelDCurran
Copy link
Member

michaelDCurran commented Oct 3, 2019

@leonardder so I am assuming isJavaWindow does however work correctly on SunAwtFrame if the app is started after NVDA starts? Or are you saying that isJavaWindow always returns false for this window?

@leonardder leonardder removed their assignment Oct 23, 2019
@lukaszgo1
Copy link
Contributor

lukaszgo1 commented Nov 18, 2019

@leonardder What is the status of your investigation? This has been brought again on NVDA users list hence my question.

@beqabeqa473
Copy link
Contributor

beqabeqa473 commented Sep 25, 2020

cannot confirm fix when using android studio.

there are times when android studio creates lags in nvda and nvda should be restarted to eliminate a lag, but after that android studio should be also restarted to make nvda read it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants