Hi Kevin,
The address for In-Process is: https://www.nvaccess.org/category/in-process/
Kind regards
Quentin.
On Sat, Nov 16, 2019 at 8:57 AM Kevin Cussick via Groups.Io <the.big.white.shepherd=googlemail.com@groups.io <mailto:googlemail.com@groups.io>> wrote:
Hi Quentin,   sorry I deleted the wrong email,   can yo send the url
for
the nvda in process again? sorry.
On 15/11/2019 07:50, Quentin Christensen wrote:
> Thanks Christo!
>
> We really appreciate the kind words!
>
> You have a great weekend too, and if you're free, feel free to
tune in
> to some of NVDACon: https://www.nvdacon.org/
>
> Kind regards
>
> Quentin.
>
> On Fri, Nov 15, 2019 at 6:46 PM Christo Vorster
> <christo.vorster.klavierstem@...
<mailto:christo.vorster.klavierstem@...>
> <mailto:christo.vorster.klavierstem@...
<mailto:christo.vorster.klavierstem@...>>> wrote:
>
>     Hi Quentin____
>
>     __ __
>
>     Thanks for the explanation. I must admit, I always was, and
still is
>     amazed tha the developers are able to update NVDA so frequently.
>     Yes, you are correct that whe all would prefer a stable
release.____
>
>     __ __
>
>     I can just repeat, thanks for the stunning work, you, and
everybody
>     involved in developing NVDA are doing. I’m sure I speak on
behalf of
>     all the users, you gave us the best possible alternative to
>     affordable speech available. I am of the opinion that NVDA is
>     probably the best speech package available.____
>
>     __ __
>
>     Thanks again, and have a nice day____
>
>     __ __
>
>     *From:*nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
>     [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>] *On Behalf
>     Of *Quentin Christensen
>     *Sent:* Friday, 15 November 2019 09:29
>     *To:* nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
<mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>>
>     *Subject:* Re: [nvda] NVDA: QUESTION____
>
>     __ __
>
>     You haven't missed anything Christo, and yes we'd normally
have the
>     third release out by now and be working on the 4th.  We're
making a
>     couple of big changes under the hood for 2019.3 - they
shouldn't be
>     too obvious when running NVDA, but they are key to future
works:____
>
>     - Speech Refactor will make it easier to update speech in
future (eg
>     to add earcons or reorder speech)____
>
>     - Moving to Python 3 is crucial, as Python 2 is about to reach
>     end-of-life and will no longer be supported from early next
year.
>     Also, people who have learnt to code Python in recent years will
>     have learnt Python 3 so this will make it easier for them to get
>     involved with NVDA.____
>
>     __ __
>
>     These changes have necessitated updates to many add-ons, and to
>     ensure that users are not left without working add-ons, we
are not
>     rushing NVDA 2019.3 but have been working with add-on
developers to
>     ensure everything transitions as smoothly as possible for
everyone
>     once NVDA 2019.3 does come out.____
>
>     __ __
>
>     If you're curious about your favourite add-ons, you can view this
>     list compiled by Joseph Lee (Thanks Joseph!) on the Add-ons site:
> https://addons.nvda-project.org/addons/nvdapy3.en.html____
>
>     __ __
>
>     You can also download the latest NVDA Alpha snapshots from
> https://www.nvaccess.org/files/nvda/snapshots/ to try them out.____
>
>     __ __
>
>     At this stage, we're expecting NVDA 2019.3, when it comes
out, will
>     be the last release this year.  We know everyone likes a new
>     release, but we're sure you like a stable release more so that's
>     what we're determined to bring you :)____
>
>     __ __
>
>     Regards____
>
>     __ __
>
>     Quentin.____
>
>     __ __
>
>     On Fri, Nov 15, 2019 at 5:10 PM Christo Vorster
>     <christo.vorster.klavierstem@...
<mailto:christo.vorster.klavierstem@...>
>     <mailto:christo.vorster.klavierstem@...
<mailto:christo.vorster.klavierstem@...>>> wrote:____
>
>         Hi Group____
>
>         ____
>
>         I have missed quite a lot of messages, thus the following
>         question____
>
>         ____
>
>         Currently I have version 2019.2.1 running. I got used to the
>         fact that, by this time of the year, version .3 was out
and we
>         were awaiting version .4. I am just curious regarding what is
>         the situation.____
>
>         ____
>
>         I don’t have a problem with 2019.2.1, but am just
curious.____
>
>         ____
>
>         Thanks for the stunning work you all are doing.____
>
>         ____
>
>         Regards____
>
>         ____
>
>         Christo Vorster (Worcester, South Africa)____
>
>
>     ____
>
>     __ __
>
>     -- ____
>
>     Quentin Christensen
>     Training and Support Manager____
>
>     __ __
>
>     Web: www.nvaccess.org <http://www.nvaccess.org>
<http://www.nvaccess.org/>____
>
>     Training: https://www.nvaccess.org/shop/____
>
>     Certification: https://certification.nvaccess.org/____
>
>     User group: https://nvda.groups.io/g/nvda____
>
>     Facebook: http://www.facebook.com/NVAccess
>     Twitter: @NVAccess <https://twitter.com/NVAccess>____
>
>     __
>
>
>
> --
> Quentin Christensen
> Training and Support Manager
>
> Web: www.nvaccess.org <http://www.nvaccess.org>
<http://www.nvaccess.org/>
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> User group: https://nvda.groups.io/g/nvda
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess <https://twitter.com/NVAccess>
>
--
Quentin Christensen
Training and Support Manager
Web: www.nvaccess.org <http://www.nvaccess.org/>
Training: https://www.nvaccess.org/shop/
Certification: https://certification.nvaccess.org/
User group: https://nvda.groups.io/g/nvda
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess <https://twitter.com/NVAccess>

Hello Gene,

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.

Best,
Henk

Op 18/11/2019 om 16:19 schreef Gene:

What happens if you unload NVDA, run the other program, then run NVDA again?

 

Gene

----- Original Message -----

From: Henk Mulder

Sent: Monday, November 18, 2019 3:33 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA freezes in IntelliJ

Hi,

Using NVDA 2019.2.1, NVDA randomly freezes when I open IntelliJ IDE
(Community edition 2019.2.4).
When it happens, NVDA hangs and won't report anything (also when
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 IntelliJ process
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 log viewer:

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 processFocusWinEvent
   File "IAccessibleHandler.pyo", line 534, in winEventToNVDAEvent
   File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
   File "NVDAObjects\__init__.pyo", line 85, in __call__
   File "NVDAObjects\IAccessible\__init__.pyo", line 412, in
findOverlayClasses
   File "JABHandler.pyo", line 707, in isJavaWindow

Best,
Henk

Hi all,

?

I?m doing a data journalism course, and one part of it (starting Wednesday) is learning basic Python. I?m using NVDA and Notepad++, and as I understand, I need to set up a way to use a command line as apparently the Windows command line alone is not so user-friendly.

?

I know I will be using the Beautiful Soup library for web-scraping, but other than that, don?t have much info yet.

?

Many thanks in advance for any assistance!

?

?ine

What happens if you unload NVDA, run the other program, then run NVDA again?

 

Gene

----- Original Message -----

From: Henk Mulder

Sent: Monday, November 18, 2019 3:33 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA freezes in IntelliJ

Hi,

Using NVDA 2019.2.1, NVDA randomly freezes when I open IntelliJ IDE
(Community edition 2019.2.4).
When it happens, NVDA hangs and won't report anything (also when
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 IntelliJ process
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 log viewer:

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 processFocusWinEvent
   File "IAccessibleHandler.pyo", line 534, in winEventToNVDAEvent
   File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
   File "NVDAObjects\__init__.pyo", line 85, in __call__
   File "NVDAObjects\IAccessible\__init__.pyo", line 412, in
findOverlayClasses
   File "JABHandler.pyo", line 707, in isJavaWindow

Best,
Henk

What happens if you unload NVDA, run the other program, then run NVDA again?

 

Gene

----- Original Message -----

From: Henk Mulder

Sent: Monday, November 18, 2019 3:33 AM

To: nvda@nvda.groups.io

Subject: [nvda] NVDA freezes in IntelliJ

Hi,

Using NVDA 2019.2.1, NVDA randomly freezes when I open IntelliJ IDE
(Community edition 2019.2.4).
When it happens, NVDA hangs and won't report anything (also when
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 IntelliJ process
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 log viewer:

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 processFocusWinEvent
   File "IAccessibleHandler.pyo", line 534, in winEventToNVDAEvent
   File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
   File "NVDAObjects\__init__.pyo", line 85, in __call__
   File "NVDAObjects\IAccessible\__init__.pyo", line 412, in
findOverlayClasses
   File "JABHandler.pyo", line 707, in isJavaWindow

Best,
Henk

On Nov 17, 2019, at 2:09 PM, Gene <gsasner@...> wrote:

That doesn't tell you if you have copied files or cut them, only text.  And unless you know the number of characters to expect to hear announced, when there is more than a small amount of text on the clipboard, the function tells you the number of characters.  What if it is text you copied earlier because, for some reason, new text isn't copied?  This feature should be changed.  It should read anything, no matter how long.  The user can stop speech with control, as always.  The screen-reader shouldn't decide for the user what is too long to read from the clipboard.  That is a complete contradiction of the philosophy of NVDA and is not allowing the user to decide what to hear and what not.

 

Gene

----- Original Message -----

From: hurrikennyandopo ...

Sent: Sunday, November 17, 2019 1:59 PM

To: nvda@nvda.groups.io

Subject: Re: [nvda] Keynote for NVDA

Hi sky 

I have not used it for years.

Are you aware that if you say copy text to the clip board with ctrl + C you can use the nvda key + C to confirm it has been copied. It will either say what you have copied or say something like to much info to read out I just can not think what it says just now or there is no content on the clip board.

I wonder if it could say it audible so you know it has been copied but also have it so it could be turned off in the add on.

Usually the short cut key is what I use to confirm if needed.

Gene nz

On 17/11/2019 7:51 pm, Sky Mundell wrote:

Hello everybody and the NVDA Conference folks. Sky here. I wanted to let you guys know that I went on TeamTalk and listened to the keynote, and it was the greatest keynote I ever heard! I am also very happy that it is being sustainable for the future and so on and so forth. As an adaptive technology specialist training blind folks how to use screen reading software I can tell you folks that I defenatly do training on NVDA, and my clients enjoy it too!  however, I am finding a shortcoming with it that I think could be addressed in future versions, and I will list it below.

Often times when I train on NVDA, one of the first things I will do is I will download the clipboard speak add-on, so that the client knows when they have copied text to the clipboard. Is there any chance that this function could be put into the core? The reason is that it would save myself from having to add the function and it would also help some of my less technically minded clients. Because often times, as we all know, the less technically minded clients want things to be able to work straight out of the box, and they’re not going to fight with their screen reader just to get something to work. Thanks, Sky.

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Giles Turnbull
Sent: Monday, November 18, 2019 6:21 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important notice on Joseph Lee's add-ons: NVDACon 2019 announcements, NVDA 2019.3 compatibility and add-on updates

Hi Joseph,

I use the screen curtain addon and defined ALT+Shift+s to trigger it. Will that shorcut still function when screen curtain is incorporated into NVDA 2019.3 or will I need to redefine it?

Thanks :)

Giles

Hi Joseph,

I use the screen curtain addon and defined ALT+Shift+s to trigger it. Will
that shorcut still function when screen curtain is incorporated into NVDA
2019.3 or will I need to redefine it?

Thanks :)

Giles

Dear NVDA community,



First, thank you to everyone who came to NVDACon 2019. A special thank
you to everyone who showed up to an informal add-on users meeting for
my add-ons.



As part of the user meeting, a number of important announcements were
made,
including:



* NVDA 2019.3 compatibility: almost all of my add-ons are compatible -
the lone exception is Screen Curtain, as the functionality is now part
of NVDA 2019.3. This add-on will be no more the day NVDA 2019.3 stable
version is released to the public.
* Add-on update releases: in the next few weeks, various add-ons will
be updated to require NVDA 2019.3. This will be done in waves:
starting with development snapshots for StationPlaylist and Windows 10
App Essentials on November 19, followed by more add-ons once NVDA
2019.3 stable version is released, ending with Add-on Updater in
February 2020.
* No going back after installing Python 3 strict add-ons: after
installing any add-on that requires NVDA 2019.3 (from my collection),
there is no going back. In particular, StationPlaylist add-on uses
parts of Python
3 that isn't backwards compatible, so going back to an earlier version
will not be possible (nor recommended).
* Several add-ons are leaving my nest: by February 1, 2020, I'll be
handing over the following add-ons to the community for further
maintenance:
Easy Table Navigator, Golden Cursor, ObjPad, SystrayList. For Golden
Cursor and SystrayList, version 4.0 is on its way, requiring NVDA 2019.3.
* Windows 10 App Essentials and October 2018 Update: the last Windows
10 App Essentials release to support Windows 10 October 2018 Update
(Version
1809) will be 20.01.x.



Special notice for StationPlaylist and Windows 10 App Essentials
snapshot
users: if you are using NVDA 2019.2.1 or earlier, you would have
received a notice about requiring NVDA 2019.3 from November 20, 2019
onwards. This will indeed happen - a snapshot destined for November
19th will require NVDA
2019.3 in any form, which will be enforced on November 20, 2019.



Thank you.

Cheers,

Joseph

That doesn't tell you if you have copied files or cut them, only text. And
unless you know the number of characters to expect to hear announced, when
there is more than a small amount of text on the clipboard, the function
tells you the number of characters. What if it is text you copied earlier
because, for some reason, new text isn't copied? This feature should be
changed. It should read anything, no matter how long. The user can stop
speech with control, as always. The screen-reader shouldn't decide for the
user what is too long to read from the clipboard. That is a complete
contradiction of the philosophy of NVDA and is not allowing the user to
decide what to hear and what not.

Gene
----- Original Message -----

From: hurrikennyandopo ...
Sent: Sunday, November 17, 2019 1:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Keynote for NVDA


Hi sky





I have not used it for years.




Are you aware that if you say copy text to the clip board with ctrl + C you
can use the nvda key + C to confirm it has been copied. It will either say
what you have copied or say something like to much info to read out I just
can not think what it says just now or there is no content on the clip
board.




I wonder if it could say it audible so you know it has been copied but also
have it so it could be turned off in the add on.




Usually the short cut key is what I use to confirm if needed.




Gene nz




On 17/11/2019 7:51 pm, Sky Mundell wrote:

Hello everybody and the NVDA Conference folks. Sky here. I wanted to let
you guys know that I went on TeamTalk and listened to the keynote, and it
was the greatest keynote I ever heard! I am also very happy that it is being
sustainable for the future and so on and so forth. As an adaptive technology
specialist training blind folks how to use screen reading software I can
tell you folks that I defenatly do training on NVDA, and my clients enjoy it
too! however, I am finding a shortcoming with it that I think could be
addressed in future versions, and I will list it below.

Often times when I train on NVDA, one of the first things I will do is I
will download the clipboard speak add-on, so that the client knows when they
have copied text to the clipboard. Is there any chance that this function
could be put into the core? The reason is that it would save myself from
having to add the function and it would also help some of my less
technically minded clients. Because often times, as we all know, the less
technically minded clients want things to be able to work straight out of
the box, and they’re not going to fight with their screen reader just to get
something to work. Thanks, Sky.

Dear NVDA community,



First, thank you to everyone who came to NVDACon 2019. A special thank you
to everyone who showed up to an informal add-on users meeting for my
add-ons.



As part of the user meeting, a number of important announcements were made,
including:



* NVDA 2019.3 compatibility: almost all of my add-ons are compatible -
the lone exception is Screen Curtain, as the functionality is now part of
NVDA 2019.3. This add-on will be no more the day NVDA 2019.3 stable version
is released to the public.
* Add-on update releases: in the next few weeks, various add-ons will
be updated to require NVDA 2019.3. This will be done in waves: starting
with
development snapshots for StationPlaylist and Windows 10 App Essentials on
November 19, followed by more add-ons once NVDA 2019.3 stable version is
released, ending with Add-on Updater in February 2020.
* No going back after installing Python 3 strict add-ons: after
installing any add-on that requires NVDA 2019.3 (from my collection), there
is no going back. In particular, StationPlaylist add-on uses parts of
Python
3 that isn't backwards compatible, so going back to an earlier version will
not be possible (nor recommended).
* Several add-ons are leaving my nest: by February 1, 2020, I'll be
handing over the following add-ons to the community for further
maintenance:
Easy Table Navigator, Golden Cursor, ObjPad, SystrayList. For Golden Cursor
and SystrayList, version 4.0 is on its way, requiring NVDA 2019.3.
* Windows 10 App Essentials and October 2018 Update: the last Windows
10 App Essentials release to support Windows 10 October 2018 Update
(Version
1809) will be 20.01.x.



Special notice for StationPlaylist and Windows 10 App Essentials snapshot
users: if you are using NVDA 2019.2.1 or earlier, you would have received a
notice about requiring NVDA 2019.3 from November 20, 2019 onwards. This
will
indeed happen - a snapshot destined for November 19th will require NVDA
2019.3 in any form, which will be enforced on November 20, 2019.



Thank you.

Cheers,

Joseph