toggle quoted messageShow quoted text
It is on a fresh install of Windows. So the JDK, JRE (both X64 and
X86) and the access bridge are freshly installed.
I know the access bridge is working, since I can access the
"Configure Java" application. I can also work with IntellliJ, ass
long as it will correctly start. But half the time it freezes when
Op 19/11/2019 om 03:48 schreef Shaun
In addition, java will not update its dlls right if they are
being used on windows 10.
So you can 1. update java, restart, then reinstall java to put
the dlls back or run narator to update java which is what I do
when updating java its not a big issue as java doesn't update
all the time.
On 19/11/2019 2:26 pm, Jaffar Sidek
Yup Java Access Bridge seems to be a problem in terms of
stability. I don't know if you are using a 64 bit machine.
If this is so, perhaps you might like to check if the
appropriate WindowsAccessBridge.dll is in the appropriate
windows/system32 or windows/SysWOW directories. so
WindowsAccessBridge-64.dll should be in the windows/system32
directory and WindowsAccessBridge.dll should be in the
windows/SysWOW directory. Cheers!
On 11/19/2019 5:51 AM, Henk Mulder
am aware of the accessibility history of IntelliJ. It is
getting better though. Partly because Android Studio is also
based on IntelliJ, and for Android Studio they do seem to work
a little bit on accessibility.
For me the choice for IntelliJ is more because that is what's
being used in industry. Since all my colleagues use IntelliJ,
and Eclipse does not support the way our project is organized,
I rather use what everyone else is using (if possible).
However the problem I have is not with IntelliJ accessibility.
I think there is a problem with NVDA and the Java access
bridge in general. I was hoping that someone might have a
solution to that.
I'm also using JDK8, since that's what I require for our
project. I am running the latest update (JDK/JRE 1.8.0_231),
so I assume I also have the most up-to-date access bridge
Op 18/11/2019 om 21:27 schreef
HI. IntelliJ Idea has had problems with accessibility
since time immemorial. Perhaps you would consider
eclipse? Or if it is Android programming you are in to,
then Android Studio? Those aren't the best accessibility
wise, but they do work much better with NVDA. Also, you
might want to check if you have the Latest version of the
Java SDK as they concequently come with the latest version
of the Java Access Bridge. I have no idea of the degree
of accessibility of versions later then version 8 though
because I have stuck to Java 8 and all it's builds since
it's inception. Cheers!
On 11/19/2019 12:19 AM, Henk
Unfortunately that won't help. IntelliJ is a Java
application. Therefore you need the Java Access bridge in
order to be able to use it with NVDA. The problem is that
the Java Access Bridge will only load if the accessibility
service is running. Thus if NVDA is not running while I
start the application, I won't be able to work with the
program since the access bridge isn't loaded.
On a similar note: if you restart NVDA while working with
the program, you also lose the access bridge and need to
restart the program as well.
Op 18/11/2019 om 16:19
What happens if you unload NVDA, run the other
program, then run NVDA again?
----- Original Message -----
Sent: Monday, November 18, 2019 3:33 AM
Subject: [nvda] NVDA freezes in IntelliJ
Using NVDA 2019.2.1, NVDA randomly freezes when I open
(Community edition 2019.2.4).
When it happens, NVDA hangs and won't report anything
switching to other applications with alt+tab). Also
IntelliJ hangs and
will not open the current project. The only thing I can
do is to start
Windows Narrator, which does keep working, and end the
via the task manager. When the IntelliJ process is
killed NVDA unfreezes.
Is there a way to make sure, or to increase the chance,
that I can start
IntelliJ without NVDA and IntelliJ locking each other?
When NVDA is back I have the following snippet in the
WARNING - watchdog._watcher (10:08:48.759):
Core frozen in stack:
File "nvda.pyw", line 231, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 889, in pumpAll
File "IAccessibleHandler.pyo", line 663, in
File "IAccessibleHandler.pyo", line 534, in
File "NVDAObjects\IAccessible\__init__.pyo", line 46,
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line
File "JABHandler.pyo", line 707, in isJavaWindow