1. nvda@nvda.groups.io
   Date   
Reader mode in Chrome?

Gerardo Corripio
 

Using latest NVDA 2019.2.1 with latest Google Chrome, is there a command to into Reader mode, like yu can with iOS on the iPHone?

Gera
Enviado desde mi iPhone SE de Telcel
Re: edge showstopper maybe

Arlene
 

H! Now if Edge has office apps you can work with off line. That, I would like if I was in a situation where there’s no wifi!  Sarah, I did get the new edge.  If you use Chrome. I find Edge is the same. I’ll play around with it later. Like Chrome it’s responsive quicker then IE.  What I do not like, you have Bing shoved at you.

 

Sent from Mail for Windows 10

 

From: Shaun Everiss
Sent: January 16, 2020 11:03 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] edge showstopper maybe

 

Well I am tryin to improve.

As for edge, it seems a mixed bad, I can't say I am total surprised but I was expecting better, just a little.

Edge has been configured.

For those that see office there are web apps which are sites in edge that can do things offline.

Edge it self does try to explain better than I am.

You can uninstall those to.

Once you link everything via your microsoft account on edge, your settings should stay so no need to reset.

 

 

On 16/01/2020 6:39 pm, Sarah k Alawami wrote:

Exactgly. I move to have shawn band form this list as well. And yes I am calling him out publicly. This is why I hardly post on this list because of the thoughtless dribble he posts, it is just utter crap and utter nonsense.

Take care and blessings. And enjoy the new edge. Can't wait to get my hands on it on mac os. It rocks there.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.

to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 15 Jan 2020, at 14:23, Kevin Cussick via Groups.Io wrote:

Yes, good post and really this is just more of the same dribble that we have had over on the windows10 list.

On 15/01/2020 21:02, Brian Vogel wrote:

On Wed, Jan 15, 2020 at 02:44 PM, Shaun Everiss wrote:

still by mentioning the words alpha or beta it implies something that is
makeshift, not secure, not stable, could trash windows, could do who knows
what.

Neither of which is accurate in the world of software development.

Alpha is simply in the earliest stages of development, and may be unstable, but seldom if ever is any of the other things.

Beta is considered to be quite stable, and things released as beta by commercial and many open source entities are considered to be possible release candidates, but will not actually be designated as such until a beta has been used "in the wild" long enough to show that there are not unsuspected issues, most of which would be minor, but possibly annoying.

Alpha software carries a high risk for possible annoyance and failure of that software itself, and very seldom takes anything else along with it.

Beta software can generally be thought of as being stable, with some possible refinements at the periphery that may be needed.   It's not uncommon for something to go from beta to release sans any changes, either.

--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

Most of the change we think we see in life is due to truths being in and out of favor.

~ Robert Frost, The Black Cottage (1914)


 
Re: Unread/Read Status of Messages Broken In Thunderbird With 2019.3 Beta 2

hurrikennyandopo ...
 

Hi


What have you got your message time out set to? Mine is set to 5 seconds otherwise I think they show as read.


In mozilla thunder bird go to tools then options then display then advanced then under there is a setting to change your time out of your messages. You might have to tab or arrow around to find it to change it.


Mine here reads the unread message as it status until I open it. I think there was a setting in thunder bird so it could also save replied etc but would have to look as have not used it for a long time.


Gene nz

On 17/01/2020 3:42 am, Ron Canazzi wrote:
Hi Clive,

For me, NVDA used to show numbers of unread messages in the tree view of folders when you arrowed over them.  With release of 2019.3 beta 2, this no longer works for me.  Many others are not having this problem, so there must be something going on with my system.


On 1/16/2020 6:44 AM, Clive Lever wrote:
Sorry if this has been covered before, but I notice that when I'm reading the list of folders in my inbox (Outlook, Office 365), in Jaws, it tells me how many unread messages there are in the folder. NVDA doesn't do this, to my knowledge. If it can say the total number of unread messages the way Jaws does, please can someone tell me how to make it do so? It's particularly useful when, say, I come back from holiday to hundreds of messages, as it tells me when the backlog is cleared.

Thanks,
Clive



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Ralf Kefferpuetz
Sent: Thursday, January 16, 2020 7:41 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Unread/Read Status of Messages Broken In Thunderbird With 2019.3 Beta 2

I'm on 68.3.1 with NVDA 2019.3 beta 2 and all message flags are read as usual.

Cheers,
   Ralf

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Ron Canazzi
Sent: Donnerstag, 16. Januar 2020 01:13
To: nvda@nvda.groups.io
Subject: Re: [nvda] Unread/Read Status of Messages Broken In Thunderbird With 2019.3 Beta 2

The last version of Thunderbird that reads the status line and the read/unread status   of messages properly is 60.9 or 60 something.


On 1/15/2020 1:06 PM, John Isige wrote:
I just downloaded NVDA 2019.3beta2 and told it to continue running. I'm
running Thunderbird 60.9.1, 32-bit if it matters. Message statuses work
fine for me with up and down arrows, I didn't even have to close and
restart Thunderbird. What do you mean by saying "last fully compatible
version"? What's broken? I admit I use Thunderbird pretty minimally, but
everything seems fine to me.


On 1/15/2020 9:56, Ron Canazzi wrote:
Hi Group,

For some reason, when I installed 2019.3 beta 2, when I read the
status line and/or navigate with up/down arrow keys, the read/unread
status of message is inconsistent or incorrect.

I wonder if anyone else is experiencing this issue.  I am using
Thunderbird 60.4--the last fully compatible version of Thunderbird.
Re: edge showstopper maybe

Shaun Everiss
 

Well I am tryin to improve.

As for edge, it seems a mixed bad, I can't say I am total surprised but I was expecting better, just a little.

Edge has been configured.

For those that see office there are web apps which are sites in edge that can do things offline.

Edge it self does try to explain better than I am.

You can uninstall those to.

Once you link everything via your microsoft account on edge, your settings should stay so no need to reset.



On 16/01/2020 6:39 pm, Sarah k Alawami wrote:

Exactgly. I move to have shawn band form this list as well. And yes I am calling him out publicly. This is why I hardly post on this list because of the thoughtless dribble he posts, it is just utter crap and utter nonsense.

Take care and blessings. And enjoy the new edge. Can't wait to get my hands on it on mac os. It rocks there.

Sarah Alawami, owner of TFFP. . For more info go to our website. This is also our libsyn page as well.

to subscribe to the feed click here

Our telegram channel is also a good place for an announce only in regard to podcasts, contests, etc.

Our discord is where you will know when we go live on youtube, twitch and mixer. Thanks Restream staff.

Finally, to become a patron and help support the podcast go here

On 15 Jan 2020, at 14:23, Kevin Cussick via Groups.Io wrote:

Yes, good post and really this is just more of the same dribble that we have had over on the windows10 list.

On 15/01/2020 21:02, Brian Vogel wrote:

On Wed, Jan 15, 2020 at 02:44 PM, Shaun Everiss wrote:

still by mentioning the words alpha or beta it implies something that is
makeshift, not secure, not stable, could trash windows, could do who knows
what.

Neither of which is accurate in the world of software development.

Alpha is simply in the earliest stages of development, and may be unstable, but seldom if ever is any of the other things.

Beta is considered to be quite stable, and things released as beta by commercial and many open source entities are considered to be possible release candidates, but will not actually be designated as such until a beta has been used "in the wild" long enough to show that there are not unsuspected issues, most of which would be minor, but possibly annoying.

Alpha software carries a high risk for possible annoyance and failure of that software itself, and very seldom takes anything else along with it.

Beta software can generally be thought of as being stable, with some possible refinements at the periphery that may be needed.   It's not uncommon for something to go from beta to release sans any changes, either.

--

Brian *-* Windows 10 Pro, 64-Bit, Version 1909, Build 18363

Most of the change we think we see in life is due to truths being in and out of favor.

~ Robert Frost, The Black Cottage (1914)
Re: Problems w/single key navigation

Jonathan COHN
 

Also, just to be sure. You are already running NVDA when you start the browser right? Browsers check for AT products on launch and only enable their acessibility layer when they detect a screen reader.
Jonathan
Re: BARD Express with NVDA still don’t get along fully

Robert Kingett
 

It works with Narrator in advanced mode but you have to navigate to the annotation column each and every time. Narrator won't read the other columns automatically like NVDA and JAWS will but it will read the full column in advanced mode.
Re: screen search

Gene
 

This is the page.  You can read about the add-on and get the version you want.
Gene

----- Original Message -----
Sent: Thursday, January 16, 2020 7:00 AM
Subject: Re: [nvda] screen search

I need the add on link please jeen

On 1/16/20, Gene <gsasner@...> wrote:
> A screen search is using something such as in JAWS, the JAWS cursor to
> search the current screen.  NVDA has no way to do this without using an
> add-on, but there is an add-on that allows you to virtualize the current
> window and thus, search the screen using the NVDA search command, control
> NVDA key f in desktop layout.  I don't know the laptop layout.
>
> I don't know the answer to the original question.  I played with the add-on
> briefly and I didn't see such an option, but also, I wasn't looking, though
> I doubt it's there.  I would suggest keeping a record in something like
> Notepad of previous search strings.  You may have to type them manually
> there, but that may be the only way to do what you want to do.
>
> Gene
> ----- Original Message -----
> From: hurrikennyandopo ...
> Sent: Wednesday, January 15, 2020 10:35 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] screen search
>
>
> Hi
>
>
>
>
> What do you mean by screen search.
>
>
>
>
> You do not mean like do a search of a web page?
>
>
>
>
> If that is the case use the nvda key + ctrl key + the letter f when the
> dialogue box comes up enter in your search term. there is also a combo box
> that will tell you your last 20 searches etc Can not remember if they can be
> saved?
>
>
>
>
> Gene nz
>
>
>
>
> On 16/01/2020 12:02 pm, Darren Harris via Groups.Io wrote:
>
>   Hi all,
>
>
>
>   Is there a way of using nvda to do a screen search whereby you can also
> store multiple search strings so you can access them at any given time?
>
>
>
>
>
Re: BARD Express with NVDA still don’t get along fully

Dave Grossoehme
 

Good Day:  Does it work with Narrator?

Dave

On 1/8/2020 6:50 AM, Gerardo Corripio wrote:
I updated my Bard Express to version2, thus I was hoping that in this new version, the issue in where the NVDA screen reader would read the entirety of the book information when on lists of books, would get resolved, but sadly it’s the same; it only reads the first few lines of the annotation. Browsing through the BARD Express View menu, I saw an item something about Screen Readers, whose shortcut is alt+q, but no go either! Whose fault is it that NVDA doesn’t get along as other screen readers with Bard Express? not everyone of us have the means to get Jaws; also as the years have gone by, the NVDA screen reader has been maturing to the point, where me personally, I enjoy using it, thus I feel that no matter which screen reader being used, we should be able to work with the same efficiency with the BARD Express app.
Any ideas or suggestions if there’s a setting maybe I haven’t thought abut changing to have the info read as it should, without having to go into the Book Details page for this?

Gera
Enviado desde mi iPhone SE de Telcel
can't stream this month's magazine on the talking computers site using edge

Rosemarie Chavarria
 

Hi, everyone,

 

Now that I've turned off the ui automation, edge works greats with NVDA but I can't stream this month's magine on the talking computer site. When I hit shift f-6 to try to open the music file, I get amazon instead. How do I correct this problem?

 

Thanks for your help in advance.

 

Rosemarie

 

 
Re: NVDA and express vpn

Angelo Sonnesso
 

Did you try Tunnel Bear?

73 N2DYN Angelo

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Vlad
Dragomir
Sent: Thursday, January 16, 2020 11:42 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA and express vpn

Hi again,

Welcome to the club! I tried the same with HMA VPN, ExpressVPN, IP Vanish, and
a few others. The best I got is: "This might take a while". Of course "a
while" turned out to be more than a year with no change at all. At least if
they could be honest and admit that they simply don't care about
accessibility, it would make our lives a little easier. *smile*

The fight continues!

Best,

Vlad.
Re: NVDA and express vpn

Vlad Dragomir
 

Hi again,

Welcome to the club! I tried the same with HMA VPN, ExpressVPN, IP Vanish, and a few others. The best I got is: "This might take a while". Of course "a while" turned out to be more than a year with no change at all. At least if they could be honest and admit that they simply don't care about accessibility, it would make our lives a little easier. *smile*

The fight continues!

Best,

Vlad.
Re: Problems w/single key navigation

Joseph Lee
 

Hi,

Sounds like NVDA isn’t recognizing web content as proper browse mode document. One way to resolve this is running COM Registration Tool: NVDA menu/Tools/Run COM Registration Fixing tool. If things go well, browse mode should work again in web browsers.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Greg Rhodes
Sent: Thursday, January 16, 2020 7:47 AM
To: NVDA Users Group <nvda@nvda.groups.io>
Subject: [nvda] Problems w/single key navigation

 

I’m running the latest version of Windows 1903 and I believe the latest version of NVDA. Single key navigation does not work for me in the Google Chrome or Firefox web browsers. I therefore was using Edge. When I downloaded the new Edge browser yesterday, single key navigation stopped working in Edge. Now I have no browsers where I can use single key navigagation. Can’t get it to work with NVDA or Narrator. Computer geeks tell me it must be a screen reader issue. Can anyone out there help? Is there a Windows 10 or screen reader setting that should be turned on or off to enable single key navigation. FYI, single key navigation does work for me in MS Word.

Thanks.

 

Greg
Problems w/single key navigation

Greg Rhodes
 

I’m running the latest version of Windows 1903 and I believe the latest version of NVDA. Single key navigation does not work for me in the Google Chrome or Firefox web browsers. I therefore was using Edge. When I downloaded the new Edge browser yesterday, single key navigation stopped working in Edge. Now I have no browsers where I can use single key navigagation. Can’t get it to work with NVDA or Narrator. Computer geeks tell me it must be a screen reader issue. Can anyone out there help? Is there a Windows 10 or screen reader setting that should be turned on or off to enable single key navigation. FYI, single key navigation does work for me in MS Word.

Thanks.

 

Greg
Re: screen search again

Joseph Lee
 

Hi,

NVDA’s find dialog is limited to places where browse mode can be invoked.

As for search history, the issue I mentioned may have to do with the GUI toolkit we are using (NVDA is powered by wxPython, the Python implementation of wxWidgets). Also, note that NVDA isn’t an English screen reader – it is used by thousands in different languages, hence if something goes odd in one input system for a language, it will lead to decisions (in some cases) to pull a feature from release until a better solution is found (such is the case with search history).

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris via Groups.Io
Sent: Thursday, January 16, 2020 7:38 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] screen search again

 

Well, window eyes had this functionality as standard. So I don’t really see what’s so different here?



On 16 Jan 2020, at 15:29, Joseph Lee <joseph.lee22590@...> wrote:



Hi,

A few months ago the combo box you are talking about (search history) did exist under development snapshots. However it was found that it didn’t allow people typing in Chinese, Japanese, Korean and additional languages to perform searches (or rather, delete search texts being typed). As a result, search history was removed.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris via Groups.Io
Sent: Thursday, January 16, 2020 12:19 AM
To: nvda@nvda.groups.io
Subject: [nvda] screen search again

 

Ok so I tried the incert ctrl plus f command. That works but if there’s a combo box to show previous search strings I can’t seem to find them.

 

Any help here?
Re: edge showstopper maybe

Davy Cuppens
 

If you want stable software, never mess with betas whatever software it is.
 

From: Gene
Sent: Wednesday, January 15, 2020 8:04 PM
Subject: Re: [nvda] edge showstopper maybe
 
What do you mean by not stable?  Not all add-ons working with it isn't a matter of stability.  it is a matter of compatibility and probably has to do with those add-ons not yet being compatible.  but it is likely stable in that it works properly in general and doesn't crash more than a stable program does.
 
I haven't tried it but in the past, I have found NVDA betas to generally be stable.
 
Gene
----- Original message -----
Sent: Wednesday, January 15, 2020 12:30 PM
Subject: Re: [nvda] edge showstopper maybe
 
Hmph.

And there we have a problem joseph.

2019.3 is not stable yet.

Not all addons I use work with it just yet.

If it comes I will have to set it up with narator.

I may try later on today to do this again because I have all the cloud
boxes here.

Is there a standalone installer for edge like there is with chrome?



On 16/01/2020 6:57 am, Joseph Lee wrote:
> Hi,
> You need to use NVDA 2019.3 beta 2 or later.
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
> Sent: Wednesday, January 15, 2020 9:53 AM
> To: nvda@nvda.groups.io
> Subject: [nvda] edge showstopper maybe
>
> Hi.
>
> There are a few big issues.
>
> I was moving round setting things up and nvda froze up completely and I had to restart it
>
> INFO - _UIAHandler.UIAHandler.MTAThreadFunc (03:58:43.407):
> UIAutomation: IUIAutomation6
> INFO - core.main (03:58:44.369):
> NVDA initialized
> ERROR - NVDAObjects.behaviors.LiveText._monitor (03:58:45.331):
> Error getting initial lines
> Traceback (most recent call last):
>     File "NVDAObjects\behaviors.pyo", line 270, in _monitor
>     File "NVDAObjects\window\winConsole.pyo", line 54, in _getTextLines
>     File "winConsoleHandler.pyo", line 126, in getConsoleVisibleLines
>     File "wincon.pyo", line 75, in GetConsoleScreenBufferInfo
> WindowsError: [Error 6] The handle is invalid.
> ERROR - eventHandler.executeEvent (06:35:56.948):
> error executing event: gainFocus on
> <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionUIA object at
> 0x05A68690> with extra args of {}
> Traceback (most recent call last):
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 598, in _getTextWithFieldsForUIARange
> COMError: (-2146233079, None, (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (06:36:24.200):
> error executing event: gainFocus on
> <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionUIA object at
> 0x05BEFD50> with extra args of {}
> Traceback (most recent call last):
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 598, in _getTextWithFieldsForUIARange
> COMError: (-2146233079, None, (None, None, None, 0, None)) ERROR - eventHandler.executeEvent (06:37:14.160):
> error executing event: gainFocus on
> <NVDAObjects.Dynamic_EditableTextWithoutAutoSelectDetectionUIA object at
> 0x0573D2D0> with extra args of {}
> Traceback (most recent call last):
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 598, in _getTextWithFieldsForUIARange
> COMError: (-2146233079, None, (None, None, None, 0, None)) WARNING - watchdog._watcher (06:39:04.387):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 628, in _getTextWithFieldsForUIARange
>
> WARNING - watchdog._watcher (06:39:19.440):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 628, in _getTextWithFieldsForUIARange
>
> WARNING - watchdog._watcher (06:39:34.496):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 590, in _getTextWithFieldsForUIARange
>
> WARNING - watchdog._watcher (06:39:49.542):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 628, in _getTextWithFieldsForUIARange
>
> WARNING - watchdog._watcher (06:40:04.601):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 432, in speakObject
>     File "speech.pyo", line 820, in speakTextInfo
>     File "NVDAObjects\UIA\__init__.pyo", line 646, in getTextWithFields
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 622, in _getTextWithFieldsForUIARange
>     File "NVDAObjects\UIA\__init__.pyo", line 628, in _getTextWithFieldsForUIARange I got this when I restarted the brouser.
>
> WARNING - watchdog._watcher (06:49:02.773):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 416, in speakObject
>     File "speech.pyo", line 289, in speakObjectProperties
>     File "baseObject.pyo", line 47, in __get__
>     File "baseObject.pyo", line 147, in _getPropertyViaCache
>     File "NVDAObjects\UIA\__init__.pyo", line 1090, in _get_keyboardShortcut
>     File "NVDAObjects\UIA\__init__.pyo", line 744, in _getUIACacheablePropertyValue
>
> WARNING - watchdog._watcher (06:49:17.822):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 416, in speakObject
>     File "speech.pyo", line 289, in speakObjectProperties
>     File "baseObject.pyo", line 47, in __get__
>     File "baseObject.pyo", line 147, in _getPropertyViaCache
>     File "NVDAObjects\UIA\__init__.pyo", line 1090, in _get_keyboardShortcut
>     File "NVDAObjects\UIA\__init__.pyo", line 744, in _getUIACacheablePropertyValue
>
> WARNING - watchdog._watcher (06:49:32.858):
> 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 490, in run
>     File "queueHandler.pyo", line 86, in pumpAll
>     File "queueHandler.pyo", line 53, in flushQueue
>     File "eventHandler.pyo", line 62, in _queueEventCallback
>     File "eventHandler.pyo", line 155, in executeEvent
>     File "eventHandler.pyo", line 92, in __init__
>     File "eventHandler.pyo", line 100, in next
>     File
> "C:\Users\shaun\AppData\Roaming\nvda\addons\easyTableNavigator\globalPlugins\easyTableNavigator.py",
> line 82, in event_gainFocus
>     File "eventHandler.pyo", line 100, in next
>     File "NVDAObjects\__init__.pyo", line 1030, in event_gainFocus
>     File "NVDAObjects\__init__.pyo", line 918, in reportFocus
>     File "speech.pyo", line 416, in speakObject
>     File "speech.pyo", line 289, in speakObjectProperties
>     File "baseObject.pyo", line 47, in __get__
>     File "baseObject.pyo", line 147, in _getPropertyViaCache
>     File "NVDAObjects\UIA\__init__.pyo", line 1090, in _get_keyboardShortcut
>     File "NVDAObjects\UIA\__init__.pyo", line 744, in _getUIACacheablePropertyValue Based on this, and even though I can get this right now I am going to uninstall it and wait.
>
> It looks like you can uninstall anyway.
>
>
>
>
>
>
>
>
>
>
Re: screen search again

Darren Harris
 

Well, window eyes had this functionality as standard. So I don’t really see what’s so different here?


On 16 Jan 2020, at 15:29, Joseph Lee <joseph.lee22590@...> wrote:



Hi,

A few months ago the combo box you are talking about (search history) did exist under development snapshots. However it was found that it didn’t allow people typing in Chinese, Japanese, Korean and additional languages to perform searches (or rather, delete search texts being typed). As a result, search history was removed.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris via Groups.Io
Sent: Thursday, January 16, 2020 12:19 AM
To: nvda@nvda.groups.io
Subject: [nvda] screen search again

 

Ok so I tried the incert ctrl plus f command. That works but if there’s a combo box to show previous search strings I can’t seem to find them.

 

Any help here?
Re: screen search again

Joseph Lee
 

Hi,

A few months ago the combo box you are talking about (search history) did exist under development snapshots. However it was found that it didn’t allow people typing in Chinese, Japanese, Korean and additional languages to perform searches (or rather, delete search texts being typed). As a result, search history was removed.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris via Groups.Io
Sent: Thursday, January 16, 2020 12:19 AM
To: nvda@nvda.groups.io
Subject: [nvda] screen search again

 

Ok so I tried the incert ctrl plus f command. That works but if there’s a combo box to show previous search strings I can’t seem to find them.

 

Any help here?
Re: NVDA and express vpn

Lenron
 

I just wish these companies wanted to make the apps accessible. I have
emailed and chatted with support from express VPN but got nowhere.

On 1/15/20, Mobeen Iqbal <mobeeniqbal@gmail.com> wrote:
I never use the bundled VPN apps as they can be rendered inaccessible
with software updates. If you use windows built in VPN client or open
VPN which most if not all VPN's support these days, you will be fine as
both approaches are accessible.

Cheers,

Mo.


On 15/01/2020 15:25, Giles Turnbull wrote:
I used Express VPN for the year between September 2018 and 2019 while
I was living in a uni hall of residence so wanted to minimise any
potential wifi snooping.

I found Express VPN very hard to use with NVDA. I figured out which
button to press to turn the VPN on (none of the buttons are spoken as
anything other than "button") and I could hear the label next to the
switch network .... but it never gave me any alternative VPN networks
other than the one it was connected to ... maybe it did list other
networks but didn't speak them ... whatever the reason Express VPN
worked as far as connecting to one single VPN network, but nothing at
all more than that.

I haven't tried using a VPN since the Express VPN experience, but do
read any posts about them on here in case something easy to use does
get suggested :)

Giles


--
Lenron Brown
Cell: 985-271-2832
Skype: ron.brown762
Re: How does One Know What Version of nvda we are running?

Chris
 

If you press nvda key+N

Arrow down to help

Then arrow up to about and press enter

The version info is there

 

 

From: Martin McCormick
Sent: 16 January 2020 14:39
To: nvda@nvda.groups.io
Subject: [nvda] How does One Know What Version of nvda we are running?

 

The Subject is the message.  Thank you.

 

Martin McCormick

 

 

 
Re: How does One Know What Version of nvda we are running?

Jackie
 

NVDA key+n > help > about.

On 1/16/20, Martin McCormick <martin.m@suddenlink.net> wrote:
The Subject is the message. Thank you.

Martin McCormick



--
Subscribe to a WordPress for Newbies Mailing List by sending a message to:
wp4newbs-request@freelists.org with 'subscribe' in the Subject field OR by
visiting the list page at http://www.freelists.org/list/wp4newbs
& check out my sites at www.brighter-vision.com & www.mysitesbeenhacked.com
12181 - 12200 of 80988  
More
Home Messages Hashtags Subgroups About Features Pricing Updates Terms Help Twitter