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

[snufas]

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]

This is just a random thought, but it seems Jaws still uses a hook into windows display code on windows start up. Could it be that they are using this instead of the access bridge? Brian bglists@blueyonder.co.uk Sent via blueyonder. Please address personal E-mail to:- briang1@blueyonder.co.uk, putting 'Brian Gaff' in the display name field. Newsgroup monitored: alt.comp.blind-users

[LeonarddeR]

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.

[snufas]

I think it is important, just get rid of this bug for ever, and that is it, java is sorted as much as it can be.

…

On 9/30/19, Leonard de Ruijter ***@***.***> wrote: 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. -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #10296 (comment)

[LeonarddeR]

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]

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]

@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?

[lukaszgo1]

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

[beqabeqa473]

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.