Date   

Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

 

I don't really use it much if ever not automatically.



On 14/10/2020 4:09 pm, Leslie wrote:

What are you using for Say All now?  Are you still supposed to use NVDA, A or another set of keys.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: Tuesday, October 13, 2020 11:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

I just updated my NVDA.

Works great 😀

I love the new feature where the touch interaction can be toggled on and off.

And NVDA definitely seems more responsive.

I am currently using Microsoft word and NVDA seems more responsive while typing, reading character by character, etc.

I love it 😀

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Tuesday, October 13, 2020 12:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

It's working great here too. I love the snappy response too.

 

 

On 10/13/2020 9:35 AM, Sharni-Lee Ward wrote:

Just updated! Everything is so so much more responsive now! It responds to my typing faster than it used to in older versions before the update to Python 3!

 

I've only noticed one thing so far, and it's not necessarily a bad thing either, just something new to adjust to. The pauses after periods are shorter. Sentences feel closer together than they did before when reading. Again, this is something I could become accustomed to with time, and isn't necessarily a problem. I do like the snappy response time very much. :)  

On 14/10/2020 1:13 am, nvda@nvda.groups.io Integration wrote:

NVDA 2020.3 Released

By NV Access

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.

Please note, after updating any software, it is a good idea to restart the computer. Restart by going to the Shutdown dialog, selecting “restart” and pressing ENTER. Updating software can change files which are in use. This can lead to instability and strange behaviour which is resolved by rebooting. This is the first thing to try if you do notice anything odd after updating.

While downloading NVDA, please consider becoming a monthly donor. Contributions like yours help NV Access continue our important work.

We also have a range of training material in the NV Access Shop to help you increase your skills with NVDA. Start with the popular Basic Training for NVDA in electronic text, audio and braille. Save with the NVDA Productivity Bundle. This includes Basic Training, all our Microsoft Office training, and telephone support.

Download NVDA 2020.3

To find out what’s new in this release, please visit What’s new in NVDA 2020.3

 

Close-up photograph of NVDA logo in notification area.

 


Re: vocaliser voice updates

 

AAh ok.

On 14/10/2020 3:32 pm, Chris Shook wrote:
I have contacted CodeFactory about this issue.
They told me that so long as you are running the latest software, which you are if you just updated, than it is fine. You have the latest voices. It's just a glitch.




Re: waterfox error

 

I am using the latest version of calibre.

I use windows 10 addon update mainly.

I have the calibre addon and toolbars explorer.

To be honest I didn't think calibre ran within the brouser.

I have the latest version and do use it from time to time for a stand alone converter but if its really a big huuuuuge issue I can probably get rid of it if I need to.

All addons are up to date and this will happen with and without addons on waterfox and nvda.

However it doesn't do anything like this with 2008 which is what I have  gone back to.

Just loaded google and it randomly crashed just as I was entering a google search.

The big thrust of that error was from garbage colecter finding over 73 unreachable objects in run, either this happens or a virtual buffer and other file os error 1700 something something.

The easiest way right now is to use water fox 2020.08.

But if this is actually calibre crashing I could probably do without it because codex uses it as stand alone I think.

I don't use it that much.

This has been going for ages and I have posted in nvaccess and waterfox without any real answer for the last month.

Every so often I try because I think I can get an answer.

Technically I probably don't really have to upgrade waterfox ever, I have an addon blocker in the form of ublock, privacy badger and https everywhere as well as noscript classic so its not like anything will necessarily jump on me.

I also never keep more than 1 net enabled program at one time and will close it otherwise.

No one has had answers and I have been talking with waterfox devs mainly.



On 14/10/2020 2:19 pm, Quentin Christensen wrote:
A number of the errors in there appear to relate to Calibre rather than Firefox.  Calibre.exe appears to be in a directory called "Calibre2" - which version are you using?  Calibre, the eBook reader / converter, is currently at version 5.2.0.

Also, are you using any NVDA add-ons?

On Wed, Oct 14, 2020 at 7:05 AM Shaun Everiss <sm.everiss@...> wrote:
Hi.

Installed nvda 2020.3, and now got this error after brousing round a
little online, this seems to happen with blogspot sites, but as I said
things continue to happen as before with latest waterfox.

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) -
MainThread (8668):
Error running speech callback
Traceback (most recent call last):
   File "speech\manager.pyc", line 669, in _handleIndex
   File "speech\commands.pyc", line 326, in run
   File "sayAllHandler.pyc", line 164, in _onLineReached
   File "sayAllHandler.pyc", line 213, in lineReached
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 477, in __init__
   File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the
client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000
(watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "watchdog.pyc", line 317, in run
   File "threading.pyc", line 552, in wait
   File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "watchdog.pyc", line 127, in _watcher
   File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "_UIAHandler.pyc", line 310, in MTAThreadFunc
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "synthDrivers\_espeak.pyc", line 190, in run
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
   File "nvda.pyw", line 215, in <module>
   File "core.pyc", line 550, in main
   File "wx\core.pyc", line 2134, in MainLoop
   File "gui\__init__.pyc", line 1050, in Notify
   File "core.pyc", line 520, in run
   File "queueHandler.pyc", line 88, in pumpAll
   File "queueHandler.pyc", line 55, in flushQueue
   File "scriptHandler.pyc", line 166, in _queueScriptCallback
   File "keyboardHandler.pyc", line 516, in executeScript
   File "inputCore.pyc", line 201, in executeScript
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method
BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed

I know I posted a dump out there, but  here is a new one.









--
Quentin Christensen
Training and Support Manager


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Leslie <soundsofmusic@...>
 

Hi Quinton,  NVDA, A still works, but I thought it might have changed to an improved way.  I did restart the computer after updating.  I’ve always thought that NVDA, A was awkward, but I’m used to it now.  I should go check What’s New after any update.  I’ve done it, but there are so many new steps that I usually can’t find what I’m looking for.  Maybe I’m just a lazy old thing. Lololol.

 

Sent from Mail for Windows 10

 

From: Quentin Christensen
Sent: Tuesday, October 13, 2020 8:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

Hi Leslie,

 

If you have NVDA setup in laptop keyboard layout, then NVDA+A should still work for say all.  If you are using NVDA in desktop keyboard layout, then the keystroke is NVDA+down arrow.

 

If you press NVDA+control+k it opens NVDA's keyboard settings and you can check or change your keyboard layout.

 

Finally, if you find it's not working, have you restarted the PC since you updated NVDA?  Try that first and see if it comes back again.

 

Kind regards

 

Quentin.

 

On Wed, Oct 14, 2020 at 2:09 PM Leslie <soundsofmusic@...> wrote:

What are you using for Say All now?  Are you still supposed to use NVDA, A or another set of keys.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: Tuesday, October 13, 2020 11:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

I just updated my NVDA.

Works great 😀

I love the new feature where the touch interaction can be toggled on and off.

And NVDA definitely seems more responsive.

I am currently using Microsoft word and NVDA seems more responsive while typing, reading character by character, etc.

I love it 😀

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Tuesday, October 13, 2020 12:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

It's working great here too. I love the snappy response too.

 

 

On 10/13/2020 9:35 AM, Sharni-Lee Ward wrote:

Just updated! Everything is so so much more responsive now! It responds to my typing faster than it used to in older versions before the update to Python 3!

 

I've only noticed one thing so far, and it's not necessarily a bad thing either, just something new to adjust to. The pauses after periods are shorter. Sentences feel closer together than they did before when reading. Again, this is something I could become accustomed to with time, and isn't necessarily a problem. I do like the snappy response time very much. :)  

On 14/10/2020 1:13 am, nvda@nvda.groups.io Integration wrote:

NVDA 2020.3 Released

By NV Access

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.

Please note, after updating any software, it is a good idea to restart the computer. Restart by going to the Shutdown dialog, selecting “restart” and pressing ENTER. Updating software can change files which are in use. This can lead to instability and strange behaviour which is resolved by rebooting. This is the first thing to try if you do notice anything odd after updating.

While downloading NVDA, please consider becoming a monthly donor. Contributions like yours help NV Access continue our important work.

We also have a range of training material in the NV Access Shop to help you increase your skills with NVDA. Start with the popular Basic Training for NVDA in electronic text, audio and braille. Save with the NVDA Productivity Bundle. This includes Basic Training, all our Microsoft Office training, and telephone support.

Download NVDA 2020.3

To find out what’s new in this release, please visit What’s new in NVDA 2020.3

 

Close-up photograph of NVDA logo in notification area.

 


 

--

Quentin Christensen
Training and Support Manager

 

 


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Quentin Christensen
 

Hi Leslie,

If you have NVDA setup in laptop keyboard layout, then NVDA+A should still work for say all.  If you are using NVDA in desktop keyboard layout, then the keystroke is NVDA+down arrow.

If you press NVDA+control+k it opens NVDA's keyboard settings and you can check or change your keyboard layout.

Finally, if you find it's not working, have you restarted the PC since you updated NVDA?  Try that first and see if it comes back again.

Kind regards

Quentin.

On Wed, Oct 14, 2020 at 2:09 PM Leslie <soundsofmusic@...> wrote:

What are you using for Say All now?  Are you still supposed to use NVDA, A or another set of keys.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: Tuesday, October 13, 2020 11:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

I just updated my NVDA.

Works great 😀

I love the new feature where the touch interaction can be toggled on and off.

And NVDA definitely seems more responsive.

I am currently using Microsoft word and NVDA seems more responsive while typing, reading character by character, etc.

I love it 😀

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Tuesday, October 13, 2020 12:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

It's working great here too. I love the snappy response too.

 

 

On 10/13/2020 9:35 AM, Sharni-Lee Ward wrote:

Just updated! Everything is so so much more responsive now! It responds to my typing faster than it used to in older versions before the update to Python 3!

 

I've only noticed one thing so far, and it's not necessarily a bad thing either, just something new to adjust to. The pauses after periods are shorter. Sentences feel closer together than they did before when reading. Again, this is something I could become accustomed to with time, and isn't necessarily a problem. I do like the snappy response time very much. :)  

On 14/10/2020 1:13 am, nvda@nvda.groups.io Integration wrote:

NVDA 2020.3 Released

By NV Access

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.

Please note, after updating any software, it is a good idea to restart the computer. Restart by going to the Shutdown dialog, selecting “restart” and pressing ENTER. Updating software can change files which are in use. This can lead to instability and strange behaviour which is resolved by rebooting. This is the first thing to try if you do notice anything odd after updating.

While downloading NVDA, please consider becoming a monthly donor. Contributions like yours help NV Access continue our important work.

We also have a range of training material in the NV Access Shop to help you increase your skills with NVDA. Start with the popular Basic Training for NVDA in electronic text, audio and braille. Save with the NVDA Productivity Bundle. This includes Basic Training, all our Microsoft Office training, and telephone support.

Download NVDA 2020.3

To find out what’s new in this release, please visit What’s new in NVDA 2020.3

 

Close-up photograph of NVDA logo in notification area.

 



--
Quentin Christensen
Training and Support Manager


Re: News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Leslie <soundsofmusic@...>
 

What are you using for Say All now?  Are you still supposed to use NVDA, A or another set of keys.

 

Sent from Mail for Windows 10

 

From: molly the blind tech lover
Sent: Tuesday, October 13, 2020 11:45 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

I just updated my NVDA.

Works great 😀

I love the new feature where the touch interaction can be toggled on and off.

And NVDA definitely seems more responsive.

I am currently using Microsoft word and NVDA seems more responsive while typing, reading character by character, etc.

I love it 😀

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Rosemarie Chavarria
Sent: Tuesday, October 13, 2020 12:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] News – NV Access - NVDA 2020.3 Released #NVAccessNewsFeed

 

It's working great here too. I love the snappy response too.

 

 

On 10/13/2020 9:35 AM, Sharni-Lee Ward wrote:

Just updated! Everything is so so much more responsive now! It responds to my typing faster than it used to in older versions before the update to Python 3!

 

I've only noticed one thing so far, and it's not necessarily a bad thing either, just something new to adjust to. The pauses after periods are shorter. Sentences feel closer together than they did before when reading. Again, this is something I could become accustomed to with time, and isn't necessarily a problem. I do like the snappy response time very much. :)  

On 14/10/2020 1:13 am, nvda@nvda.groups.io Integration wrote:

NVDA 2020.3 Released

By NV Access

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.

Please note, after updating any software, it is a good idea to restart the computer. Restart by going to the Shutdown dialog, selecting “restart” and pressing ENTER. Updating software can change files which are in use. This can lead to instability and strange behaviour which is resolved by rebooting. This is the first thing to try if you do notice anything odd after updating.

While downloading NVDA, please consider becoming a monthly donor. Contributions like yours help NV Access continue our important work.

We also have a range of training material in the NV Access Shop to help you increase your skills with NVDA. Start with the popular Basic Training for NVDA in electronic text, audio and braille. Save with the NVDA Productivity Bundle. This includes Basic Training, all our Microsoft Office training, and telephone support.

Download NVDA 2020.3

To find out what’s new in this release, please visit What’s new in NVDA 2020.3

 

Close-up photograph of NVDA logo in notification area.

 


Re: Microsoft Edge Internet Explorer mode conflict with NVDA

Scott Salzman
 

I don't have a solution, but I think I have an explanation for what is happening "under the hood", when different browsers treat RSS feeds differently. 

 

HTML (HyperText Markup Language) evolved along with web browsers for the specific purpose of coding web pages so that they can be read in various ways, including via screen readers or visually.  XML (Extensible Markup Language) is a generic markup language and is mostly used to store data, and to transmit that data, like when you follow a link to an RSS feed.  Since XML is a generic markup language, in order to present an XML document in a way that's convenient to read, it has to be used with an XSLT stylesheet (Extensible Stylesheet Language Transformations).  XSLT stylesheets are used to transform XML files into other formats, like into HTML for example, which would make them easier and more efficient to read.  So, you could imagine an XSLT stylesheet that would take all those tags or fields in an RSS feed, and map them to things like headings, links, etc.  That could be a good reading experience.

 

When you read an XML file, like an RSS feed, in Firefox, Firefox appears to apply a very basic XSLT stylesheet to it.  So when I read the Fictional RSS feed in Firefox, some of the XML tags get transformed into buttons, and I can navigate with some very basic efficiency using NVDA.  But I wouldn't say that this gives the RSS feed much of a structure that I can easily understand.

 

When you read an XML file in Chrome, Chrome doesn't appear to apply any XSLT stylesheet to it, which would explain why reading an RSS feed using Chrome is like reading a plain text file, with no real structure that a screen reader like NVDA can use.  I don't have Internet Explorer on my laptop, but if you have a better reading experience with it than with Chrome, then it's almost certain that Internet Explorer is also applying an XSLT stylesheet to XML files.

 

Unfortunately, I don't know how to view, modify, or install XSLT stylesheets in web browsers, but maybe this will give someone an idea about how to improve the experience of reading an XML file directly in a web browser.

 

I hope at least the explanation was helpful in some way.

 

Scott

 

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Louise Pfau via groups.io
Sent: Tuesday, October 13, 2020 12:05 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Microsoft Edge Internet Explorer mode conflict with NVDA

 

Hi.  I was able to use Internet Explorer to read the feed correctly, as well as the other ones that use xml.  I didn't know if Internet Explorer would still work after its end-of-life date.  I'll try removing the trailing text like "rss" or "feed" as suggested in an earlier message in this thread.  A couple of the websites I use don't date the podcast episodes on the regular page, so I like the feeds in those cases.

Thanks,

Louise


Re: vocaliser voice updates

Chris Shook
 

I have contacted CodeFactory about this issue.
They told me that so long as you are running the latest software, which you are if you just updated, than it is fine. You have the latest voices. It's just a glitch.


Re: Issue with tab key under 2020.3

Quentin Christensen
 

Also if you haven't yet, try rebooting the computer - we occasionally see weird random issues after people update NVDA (or any software) and before they restart the PC.

If Gene's suggestion doesn't work and you can still reproduce a new issue after rebooting, do please let us know.

Kind regards

Quentin.

On Wed, Oct 14, 2020 at 10:52 AM Gene <gsasner@...> wrote:
Try pressing alt once and see if that solves the problem.  I don't recall
just what alt does but it is something like to show or hide the interface.
It’s a toggle.

Gene
-----Original Message-----
From: Marcia Yale
Sent: Tuesday, October 13, 2020 6:06 PM
To: nvda@nvda.groups.io
Subject: [nvda] Issue with tab key under 2020.3

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking
this was an incompatibility issue, but it didn't solve the problem. I'm
using Windows 7.

Marcia Yale
It is not our differences that divide us. It is our inability to recognize,
accept, and celebrate those differences.
Audre Lorde















--
Quentin Christensen
Training and Support Manager


Re: Issue with tab key under 2020.3

Scott Salzman
 

If that doesn't work, the Zoom keyboard shortcuts page says that pressing Control + Alt + Shift will move focus to Zoom's meeting controls.

 

Scott

 

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gene via groups.io
Sent: Tuesday, October 13, 2020 7:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Issue with tab key under 2020.3

 

Try pressing alt once and see if that solves the problem.  I don't recall just what alt does but it is something like to show or hide the interface.

It’s a toggle.

 

Gene

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

From: Marcia Yale

Sent: Tuesday, October 13, 2020 6:06 PM

To: nvda@nvda.groups.io

Subject: [nvda] Issue with tab key under 2020.3

 

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking this was an incompatibility issue, but it didn't solve the problem. I'm using Windows 7.

 

Marcia Yale

It is not our differences that divide us. It is our inability to recognize, accept, and celebrate those differences.

Audre Lorde

 

 

 

 

 

 

 

 

 

 

 

 


Re: Updating NVDA

Quentin Christensen
 

NVDA checks for updates roughly once a day - so if you are active on the list or follow NV Access on social media, you may well see the posts about a new version coming out before your copy goes off to look for it.  That manually running the check for updates feature found the new version indicates that NVDA can check for updates and find the new version, so it likely would have prompted you maybe later in the day or the next day if you hadn't tried earlier.  We could set it to check more often I'm sure, but given we release usually four updates a year, it's arguably not worth it just to try to get in before you see it on the list here :)


On Wed, Oct 14, 2020 at 8:22 AM Kerryn Gunness via groups.io <k_gunness=yahoo.ca@groups.io> wrote:
i go the same as brian and also i check for updates and do the update there
 
----- Original Message -----
Sent: Tuesday, October 13, 2020 2:11 PM
Subject: Re: [nvda] Updating NVDA

I have not come across this, specifically, but my decades of dealing with all sorts of software have shown me that, over time, a lot of software that's been updated, and particularly repeatedly, via "install over" updates often gets wonky.

If/when they do, I simply uninstall them entirely using Control Panel, then install the updated version separately afterward.  This solves these issues in almost all cases.

NVDA makes this particularly easy, since your user data is stored in your own AppData folder, so any configuration changes you've made, add-ons you've installed, etc., are all still there when you do a fresh install.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 



--
Quentin Christensen
Training and Support Manager


Re: waterfox error

Quentin Christensen
 

A number of the errors in there appear to relate to Calibre rather than Firefox.  Calibre.exe appears to be in a directory called "Calibre2" - which version are you using?  Calibre, the eBook reader / converter, is currently at version 5.2.0.

Also, are you using any NVDA add-ons?

On Wed, Oct 14, 2020 at 7:05 AM Shaun Everiss <sm.everiss@...> wrote:
Hi.

Installed nvda 2020.3, and now got this error after brousing round a
little online, this seems to happen with blogspot sites, but as I said
things continue to happen as before with latest waterfox.

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) -
MainThread (8668):
Error running speech callback
Traceback (most recent call last):
   File "speech\manager.pyc", line 669, in _handleIndex
   File "speech\commands.pyc", line 326, in run
   File "sayAllHandler.pyc", line 164, in _onLineReached
   File "sayAllHandler.pyc", line 213, in lineReached
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 477, in __init__
   File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the
client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program
Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000
(watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "watchdog.pyc", line 317, in run
   File "threading.pyc", line 552, in wait
   File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "watchdog.pyc", line 127, in _watcher
   File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "_UIAHandler.pyc", line 310, in MTAThreadFunc
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "threading.pyc", line 870, in run
   File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
   File "threading.pyc", line 890, in _bootstrap
   File "threading.pyc", line 926, in _bootstrap_inner
   File "synthDrivers\_espeak.pyc", line 190, in run
   File "queue.pyc", line 170, in get
   File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
   File "nvda.pyw", line 215, in <module>
   File "core.pyc", line 550, in main
   File "wx\core.pyc", line 2134, in MainLoop
   File "gui\__init__.pyc", line 1050, in Notify
   File "core.pyc", line 520, in run
   File "queueHandler.pyc", line 88, in pumpAll
   File "queueHandler.pyc", line 55, in flushQueue
   File "scriptHandler.pyc", line 166, in _queueScriptCallback
   File "keyboardHandler.pyc", line 516, in executeScript
   File "inputCore.pyc", line 201, in executeScript
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method
BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of
<virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
   File "scriptHandler.pyc", line 208, in executeScript
   File "browseMode.pyc", line 451, in <lambda>
   File "browseMode.pyc", line 407, in _quickNavScript
   File "documentBase.pyc", line 27, in _get_selection
   File "documentBase.pyc", line 24, in makeTextInfo
   File "virtualBuffers\__init__.pyc", line 207, in __init__
   File "textInfos\offsets.pyc", line 472, in __init__
   File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed

I know I posted a dump out there, but  here is a new one.









--
Quentin Christensen
Training and Support Manager


Re: Issue with tab key under 2020.3

Gene
 

Try pressing alt once and see if that solves the problem. I don't recall just what alt does but it is something like to show or hide the interface. It’s a toggle.

Gene

-----Original Message-----
From: Marcia Yale
Sent: Tuesday, October 13, 2020 6:06 PM
To: nvda@nvda.groups.io
Subject: [nvda] Issue with tab key under 2020.3

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking
this was an incompatibility issue, but it didn't solve the problem. I'm
using Windows 7.

Marcia Yale
It is not our differences that divide us. It is our inability to recognize,
accept, and celebrate those differences.
Audre Lorde


Issue with tab key under 2020.3

Marcia Yale
 

I can no longer tab around in Zoom. I have disabled the Zoom add-on thinking
this was an incompatibility issue, but it didn't solve the problem. I'm
using Windows 7.

Marcia Yale
It is not our differences that divide us. It is our inability to recognize,
accept, and celebrate those differences.
Audre Lorde


News – NV Access - NVDA 2020.3 Released #nvaccessnewsfeed

Quentin Christensen
 

NV Access is pleased to announce that version 2020.3 of NVDA, the free screen reader for Microsoft Windows, is now available for download. We encourage all users to upgrade to this version.

NVDA 2020.3 includes several large improvements to stability and performance, particularly in Microsoft Office applications. There are new settings to toggle touchscreen support and graphics reporting. The existence of marked (highlighted) content can be reported in browsers, and there are new German braille tables.


For the full release information and to download, please visit: https://www.nvaccess.org/post/nvda-2020-3/


Kind regards


Quentin.


--
Quentin Christensen
Training and Support Manager


Re: Updating NVDA

Kerryn Gunness <k_gunness@...>
 


i go the same as brian and also i check for updates and do the update there
 

----- Original Message -----
Sent: Tuesday, October 13, 2020 2:11 PM
Subject: Re: [nvda] Updating NVDA

I have not come across this, specifically, but my decades of dealing with all sorts of software have shown me that, over time, a lot of software that's been updated, and particularly repeatedly, via "install over" updates often gets wonky.

If/when they do, I simply uninstall them entirely using Control Panel, then install the updated version separately afterward.  This solves these issues in almost all cases.

NVDA makes this particularly easy, since your user data is stored in your own AppData folder, so any configuration changes you've made, add-ons you've installed, etc., are all still there when you do a fresh install.

--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Re: waterfox error

 

Shaun,

              Please read the following, from the Admin Notice entitled, List Updates: Please Read  (Sent April 11, 2020):

  • Speaking of logs, we should avoid sending long logs to this list.
    • Logs may contain personal information to your system, your set-up, or possibly keystrokes you press, etc.
    • It is not expected that users on this list will know how to read logs, or that they will dissect those logs for you to determine the issue. Please reach out to NVAccess directly. No doubt there is already a process in place for this, however we shouldn't ask users to post logs to this list.

I am asking you, and all other members, not to post logs, or even parts of logs, to this group.  It's not a developers group, there are few here who can possibly decipher logs.  If an issue is believed to be a problem with NVDA, then, as directed, "please reach out to NVAccess directly," by filing an issue [AKA bug] report.
--

Brian - Windows 10 Pro, 64-Bit, Version 2004, Build 19041  

It’s hard waking up and realizing it’s not always black and white.

     ~ Kelley Boorn

 


Re: vocaliser voice updates

 

Hmph, Well I just downloaded and installed the launcher, and got told about updates to vices but left these alone now.

Its up to date.

Thing is it never told me there was an update at all eloquence is also updated but I never knew.



On 13/10/2020 10:51 pm, mattias wrote:

The latest vocalizer sapi are

1.9.0

I downloaded it and no notification about updates

Skickades från E-post för Windows 10

 

Från: Shaun Everiss
Skickat: den 13 oktober 2020 08:15
Till: nvda@nvda.groups.io
Ämne: [nvda] vocaliser voice updates

 

Hi.

 

I have the sapi vocaliser installed.

 

I just downloaded the latest launcher from atguys.

 

There are several voices that state they need updates but there is no

update button.

 

So I uninstalled all voices and reinstalled them again but still get

notifications that some voices have updates.

 

Also tried to change activation status for one system and got an cert

error so maybe I need to wait for code factory to renew their ssl.

 

 

 

 

 

 

 


waterfox error

 

Hi.

I may have fixed my own issue.

At least I can't get it working or failing like this right now.

I toggled say all and the issue stopped at least I think its stopped.

I don't need say all to load, so maybe thats my issue.


waterfox error

 

Forgot the dump

ERROR - speech.manager.SpeechManager._handleIndex (08:47:46.568) - MainThread (8668):
Error running speech callback
Traceback (most recent call last):
  File "speech\manager.pyc", line 669, in _handleIndex
  File "speech\commands.pyc", line 326, in run
  File "sayAllHandler.pyc", line 164, in _onLineReached
  File "sayAllHandler.pyc", line 213, in lineReached
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 477, in __init__
  File "virtualBuffers\__init__.pyc", line 225, in _getStoryLength
OSError: [WinError 1775] A null context handle was passed from the client to the host during a remote procedure call
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductName
WARNING - fileUtils.getFileVersionInfo (08:54:07.529) - Dummy-1 (10332):
Invalid or unavailable version info attribute for 'C:\\Program Files\\Calibre2\\calibre.exe': ProductVersion
ERROR - watchdog._watcher (09:01:26.115) - watchdog (10764):
Core frozen in stack!
INFO - watchdog._watcher (09:01:26.119) - watchdog (10764):
Listing stacks for Python threads:
Python stack for thread 13000 (watchdog.CancellableCallThread.execute(<_FuncPtr object at 0x00BA6828>)):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "watchdog.pyc", line 317, in run
  File "threading.pyc", line 552, in wait
  File "threading.pyc", line 296, in wait

Python stack for thread 10764 (watchdog):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "watchdog.pyc", line 127, in _watcher
  File "watchdog.pyc", line 62, in getFormattedStacksForAllThreads

Python stack for thread 6332 (winInputHook):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "winInputHook.pyc", line 79, in hookThreadFunc

Python stack for thread 9848 (_UIAHandler.UIAHandler.MTAThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "_UIAHandler.pyc", line 310, in MTAThreadFunc
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 10040 (braille._BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "threading.pyc", line 870, in run
  File "braille.pyc", line 2187, in func

Python stack for thread 9660 (synthDrivers._espeak.BgThread):
  File "threading.pyc", line 890, in _bootstrap
  File "threading.pyc", line 926, in _bootstrap_inner
  File "synthDrivers\_espeak.pyc", line 190, in run
  File "queue.pyc", line 170, in get
  File "threading.pyc", line 296, in wait

Python stack for thread 8668 (MainThread):
  File "nvda.pyw", line 215, in <module>
  File "core.pyc", line 550, in main
  File "wx\core.pyc", line 2134, in MainLoop
  File "gui\__init__.pyc", line 1050, in Notify
  File "core.pyc", line 520, in run
  File "queueHandler.pyc", line 88, in pumpAll
  File "queueHandler.pyc", line 55, in flushQueue
  File "scriptHandler.pyc", line 166, in _queueScriptCallback
  File "keyboardHandler.pyc", line 516, in executeScript
  File "inputCore.pyc", line 201, in executeScript
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets

ERROR - scriptHandler.executeScript (09:01:34.119) - MainThread (8668):
error executing script: <bound method BrowseModeTreeInterceptor.addQuickNav.<locals>.<lambda> of <virtualBuffers.gecko_ia2.Gecko_ia2 object at 0x013FE950>> with gesture 'h'
Traceback (most recent call last):
  File "scriptHandler.pyc", line 208, in executeScript
  File "browseMode.pyc", line 451, in <lambda>
  File "browseMode.pyc", line 407, in _quickNavScript
  File "documentBase.pyc", line 27, in _get_selection
  File "documentBase.pyc", line 24, in makeTextInfo
  File "virtualBuffers\__init__.pyc", line 207, in __init__
  File "textInfos\offsets.pyc", line 472, in __init__
  File "virtualBuffers\__init__.pyc", line 212, in _getSelectionOffsets
OSError: [WinError 1726] The remote procedure call failed

8421 - 8440 of 86439