Date   

Re: accessible sms texting from windows with NVDA

Ervin, Glenn
 

You cannot.
You will have to find out from the person you want to text.
Glenn

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Antony Stone
Sent: Thursday, August 30, 2018 4:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible sms texting from windows with NVDA

I still don't understand how you can work out which domain to use just from knowing the phone number, even if a domain exists for the service provider.

Antony.

On Thursday 30 August 2018 at 22:23:09, Ervin, Glenn wrote:

Well, I can't tell you for outside the US, but I can't imagine that
they don't. But perhaps it is using another company's towers.
For example, I'm on Selectel, yet I use the Verizon domain.
So it's likely using the domain for who's towers it rides on.
Glenn


-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Antony
Stone
Sent: Thursday, August 30, 2018 3:15 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible sms texting from windows with NVDA

I don't believe that "all cell companies have domains for eMailing to"
is globally true.

For example, can you find a domain for Vodafone UK?

Also, how do you know which provider's domain you need to send the
message to when all you know is the phone number?


Antony.

On Thursday 30 August 2018 at 22:08:58, Ervin, Glenn wrote:
Well, if you have eMail on your phone, you can text people via eMail
by sending an eMail message to 10-digit-number@the domain For
example, to text to a cell phone on Verizon, you eMail to:
5555555555@...
All cell companies have domains for eMailing to.
Glenn

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Aman
Singer
Sent: Thursday, August 30, 2018 10:22 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible sms texting from windows with NVDA

Hi,

If you have an Android device, try Pulse SMS http://www.pulsesms.com/
Its web site works well though, in my experience, the app doesn't.
I know of no way to do this from the iPhone or another phone type,

unfortunately. Obviously, if you want to do this from a number other
than that of your phone, that is, if you don't care about your SMS
appearing from, and replies to those messages going to, a number
different from your own phone number, you can use any of the VOIP
services. See, just for accessible examples
http://www.callcentric.com http://www.les.net HTH, Aman



-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
Brian's Mail list account via Groups.Io Sent: Thursday, August 30,
2018
10:52 AM To: nvda@nvda.groups.io
Subject: Re: [nvda] accessible sms texting from windows with NVDA

The problem is, I need to do it in Europe.

Brian

----- Original Message -----
From: "Hope Williamson via Groups.Io" <isepic=lavabit.com@groups.io>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 30, 2018 2:43 PM
Subject: Re: [nvda] accessible sms texting from windows with NVDA


Hi, I'm pretty sure you can use email to do this if you get the
carrier's address right. Here's a link on how to do this.
https://www.digitaltrends.com/mobile/how-to-send-a-text-from-your-em
ail-a cc ount/ Basically, you open up your email client and put the
number you're sending to in followed by the carriers SMS gateway
address.

On 8/30/2018 6:33 AM, Dan Beaver wrote:
Hi,


I have been looking into doing this. However, there are so many
choices I am uncertain which to choose.


Has anyone else figured out any of the apps and services that are
accessible using NVDA to do SMS texting from a Windows system? If
so which are accessible and easy to use?


Thanks.


Dan Beaver
--
Perfection in design is achieved not when there is nothing left to add, but rather when there is nothing left to take away.

- Antoine de Saint-Exupery

Please reply to the list;
please *don't* CC me.


Issue with Firefox

 

To all lister
Using NVDA 2018.2.1 with Firefox 61.2.0 (portable version), Recently I surfed a website created using drupal. When I press E to jump to an edit field, and press Space to switch to focus mode, NVDA sometimes responds slowly, or lose the focus. Thus I might activate the wrong object on the web. Don't know this is the problem from NVDA with that firefox version or not so I post here. If this is an issue, hope this would be fixed. If anybody know how to solve, please show me the step.
Cuong
----------------
Dang Manh Cuong
 The Assistive technology specialist
 Sao Mai Vocational and assistive center for the blind
52/22 Huynh Thien Loc St., Hoa Thanh ward, Tan Phu dist., HCM, Vietnam.
 Tel: +8428 7302-4488
 E-mail: vanphong@...; congnghe@...
 Facebook: https://www.facebook.com/saomaicenterfortheblind
 Website: http://www.trungtamsaomai.org; http://www.saomaicenter.org  Mobile / Zalo: +84 902-572-300
 E-mail: dangmanhcuong@...; cuong@...
 Skype name: dangmanhcuong
 facebook: http://facebook.com/dangmanhcuong
 Twitter: @ManhCuongTech


Re: media access team OE Classic accessible spell checker

 

Not sure exactly, but looking at the release notes below, there's 1 bit about email security being improved. The link is below. I'd look in the help section if I were you but I wasn't able to find much. I do know that IMAP is not supported, so you absolutely have to connect via POP, which is a deal breaker for me. I'm sticking with TB for now, mainly because my TB runs from my dropbox so I never need to install it again.


https://www.oeclassic.com/news


OE Classic accessible spell checker

 

That bit about the spell checker not being available in the free version of OE classic? I get it that people hate thunderbird, but this isn't for me. I'm sticking with TB and windows mail and all of these. I'm including this here so that other people can learn what accessibility enhancements are being done. I included their email before the message, too.


phazze@...


In today's update of OE Classic we've added and improved the spell checker. It is now available for Windows 7 and earlier and what is relevant for the accessibility is that it opens in a new window, like a traditional spell checker so each word which is misspelled can be reviewed. To open it you can use F7 key on the keyboard.


The spell checker is the latest addition to the Pro version and will not be available in the free version (version 2.9, released on 2018-09-04). Further work on accessibility will be done as well. Also, we figured that the accelerator keys would also be useful so they can too be used to trigger the buttons such as Alt+I to press the Ignore button.

We also plan spell checker as you type. Of course, the usual spell check as you type is not of much use to blind users as it underlines the misspelled words with the red color. This of course cannot be seen. But, what we plan is to add a sound notification (like a bell or another configurable sound) so when each word is misspelled as soon as you move on to the next word, the previous one will sound the notification sound. The sound will be configurable via options (or no sound, if the user doesn't prefer to have one and just wants to use the F7-key spell checker). This is not implemented yet, but we do plan it as there is a good number of users who want to spell check as they type and adding a sound at the same time when a word is marked with the red color is just a minor addition to the program so not a big deal to implement, and we can understand how that might be useful.

best regards,
Zvonko Tesic

---------------------------------
A perfect replacement for Outlook Express and Windows (Live) Mail:
www.oeclassic.com

OE Classic on Facebook and Twitter:
www.facebook.com/oeclassic
www.twitter.com/infobytehr

yEnc and multipart decoder for Outlook Express newsgroups at:
www.ydecode.com
---------------------------------


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Brian's Mail list account <bglists@...>
 

Well I often see a similar effect if I close Word, but the freeze is less than five seconds normally, and yes its always been around on xp and 7. Even on fast machines so I'm thinking it might be bit of a red herring. I can look at a log and find quite a few core frozen in stack items, but often they are so fleeting that if they cause any problem, it might be no reading of a web page or no indication of where you are, ie unknown, and you can usually recover it by making things refresh.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, September 04, 2018 4:28 AM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application


I'm not sure this is a problem. It is very common, when I close a program that I am not actually in any program. I may hear something when I read the title bar suchh as the name of the program I was just in or some related name. If I go to the desktop, everything is as it should be and if I alt tab around, everything is normal with no window open that shouldn't be. This is with Windows XP. I use Windows 7 but not with enough use or variety of use to say if this happens in that version.

Is the original problem as I described or is it that NVDA stops speaking no matter what you do and you must close and run it again?

Gene
----- Original message -----

From: Don H
Sent: Monday, September 03, 2018 8:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application


Just tried to duplicate this. Indeed after closing the system information with alt f4 it seems that NVDA goes silent. after the alt f4 is pressed Nvda says unknown. Sighted help says I am back to the desktop and nothing is shown besides my normal desktop. However if you hit windows key m speech returns. Seems that something is open that is minimized by windows key m.


On 9/3/2018 7:56 PM, Quentin Christensen wrote:

Takuya,


Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled? If so, have you checked that you are using the most up to date version of any addons?


And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?


If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps




Kind regards


Quentin.










On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:

I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:

>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
> File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
> File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
> File "nvda.pyw", line 214, in <module>
>
> File "core.pyo", line 495, in main
>
> File "wx\core.pyo", line 2134, in MainLoop
>
> File "gui\__init__.pyo", line 963, in Notify
>
> File "core.pyo", line 466, in run
>
> File "queueHandler.pyo", line 83, in pumpAll
>
> File "queueHandler.pyo", line 50, in flushQueue
>
> File "eventHandler.pyo", line 62, in _queueEventCallback
>
> File "eventHandler.pyo", line 147, in executeEvent
>
> File "eventHandler.pyo", line 160, in doPreGainFocus
>
> File "api.pyo", line 107, in setFocusObject
>
> File "baseObject.pyo", line 34, in __get__
>
> File "baseObject.pyo", line 115, in _getPropertyViaCache
>
> File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
> File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
> File "winUser.pyo", line 429, in getClassName
>
>
>
>










--

Quentin Christensen
Training and Support Manager


Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/


www.nvaccess.org

Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess


Re: Fw: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook

Christo de Klerk
 

Hello again

To make things absolutely clear: I was referring to the status indicators spoken when you arrow up and down a list of messages in MS Outlook. Unread is currently the only one spoken, but in about May Replied and Forwarded as well as

read receipts and associated drafts were also announced, at least in the snapshot I mentioned in an earlier e-mail. In fact, a friend of mine has rolled back to that snapshot because these announcements are important to him in his work.


Kind regards


Christo




On 2018/09/04 01:32 PM, Brian's Mail list account via Groups.Io wrote:
see below from Mick.
----- Original Message ----- From: "Michael Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>
Sent: Tuesday, September 04, 2018 12:07 AM
Subject: Re: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook


Do they mean replied/forwarded, or unread?


My testing shows that unread is still fine. Replied/forwarded tried to be supported several times but has always failed with various languages and has never made it into an official version of NVDA.


Mick



On 31/08/2018 1:01 am, Brian's Mail list account BY via Nvda-devel wrote:
Hi saw the message below and thought, as a new nvda is imminent maybe somebody might like to find out what is going on here. I cannot myself test it as do not have the versions needed.
I have posted that I do not think wx4 has anything to do with it, more likely yet another outlook related quirk.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Christo de Klerk" <christodeklerk@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 30, 2018 10:44 AM
Subject: [nvda] NVDA recent snapshots not reading message status in Outlook


Hello all


I have noticed that the NVDA snapshots of the past two months or so no longer read message statuses in Outlook. This is true of Outlook 2013, Outlook 2016 and Outlook in Office 365. Could this be an unpleasant side-effect of the migration to WXPython 4? Can we look forward to this being fixed in the not too distant future. It really was such a helpful feature when NVDA used to announce message statuses.


Kind regards


Christo







------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel







Fw: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook

Brian's Mail list account <bglists@...>
 

See below

----- Original Message -----
From: "Michael Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>
Cc: "Brian's Mail list account BY" <bglists@...>
Sent: Tuesday, September 04, 2018 12:07 AM
Subject: Re: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook


Do they mean replied/forwarded, or unread?


My testing shows that unread is still fine. Replied/forwarded tried to be supported several times but has always failed with various languages and has never made it into an official version of NVDA.


Mick



On 31/08/2018 1:01 am, Brian's Mail list account BY via Nvda-devel wrote:
Hi saw the message below and thought, as a new nvda is imminent maybe somebody might like to find out what is going on here. I cannot myself test it as do not have the versions needed.
I have posted that I do not think wx4 has anything to do with it, more likely yet another outlook related quirk.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Christo de Klerk" <christodeklerk@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 30, 2018 10:44 AM
Subject: [nvda] NVDA recent snapshots not reading message status in Outlook


Hello all


I have noticed that the NVDA snapshots of the past two months or so no longer read message statuses in Outlook. This is true of Outlook 2013, Outlook 2016 and Outlook in Office 365. Could this be an unpleasant side-effect of the migration to WXPython 4? Can we look forward to this being fixed in the not too distant future. It really was such a helpful feature when NVDA used to announce message statuses.


Kind regards


Christo




------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Fw: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook

Brian's Mail list account <bglists@...>
 

see below from Mick.

----- Original Message -----
From: "Michael Curran" <mick@...>
To: "NVDA screen reader development" <nvda-devel@...>
Sent: Tuesday, September 04, 2018 12:07 AM
Subject: Re: [Nvda-devel] Fw: [nvda] NVDA recent snapshots not reading message status in Outlook


Do they mean replied/forwarded, or unread?


My testing shows that unread is still fine. Replied/forwarded tried to be supported several times but has always failed with various languages and has never made it into an official version of NVDA.


Mick



On 31/08/2018 1:01 am, Brian's Mail list account BY via Nvda-devel wrote:
Hi saw the message below and thought, as a new nvda is imminent maybe somebody might like to find out what is going on here. I cannot myself test it as do not have the versions needed.
I have posted that I do not think wx4 has anything to do with it, more likely yet another outlook related quirk.
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Christo de Klerk" <christodeklerk@...>
To: <nvda@nvda.groups.io>
Sent: Thursday, August 30, 2018 10:44 AM
Subject: [nvda] NVDA recent snapshots not reading message status in Outlook


Hello all


I have noticed that the NVDA snapshots of the past two months or so no longer read message statuses in Outlook. This is true of Outlook 2013, Outlook 2016 and Outlook in Office 365. Could this be an unpleasant side-effect of the migration to WXPython 4? Can we look forward to this being fixed in the not too distant future. It really was such a helpful feature when NVDA used to announce message statuses.


Kind regards


Christo




------------------------------------------------------------------------------

Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
Nvda-devel@...
https://lists.sourceforge.net/lists/listinfo/nvda-devel


Re: NVDA, latest alpha works much better in Win10 mail app!

Chris
 

Hmm, maybe, seems better, whether that’s down to the app essentials addon or the latest mail app update, I really couldn’t say for sure where the improvement lies

 

 

From: David Moore
Sent: 04 September 2018 01:32
To: nvda@nvda.groups.io
Subject: [nvda] NVDA, latest alpha works much better in Win10 mail app!

 

Hi all!

I can’t believe what the newest Window Apps Essential’s did for the Win10 Mail app.

I have been hearing the same line repeat as I arrow down through my messages that I am about to send. I am using latest alpha version. I still have a little trouble navigating letter by letter; it says the same letter a few times, but it is so much better!

I could not make corrections at all, because I could not navigate character by character or word by word.

It is all fixed now, and I am so glad!

Do any of you notice a change in how the Win10 Mail app works?

Take care, guys!

David Moore

 

Sent from Mail for Windows 10

 

 


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Gene
 

I'm not sure this is a problem.  It is very common, when I close a program that I am not actually in any program.  I may hear something when I read the title bar suchh as the name of the program I was just in or some related name.  If I go to the desktop, everything is as it should be and if I alt tab around, everything is normal with no window open that shouldn't be.  This is with Windows XP.  I use Windows 7 but not with enough use or variety of use to say if this happens in that version. 
 
Is the original problem as I described or is it that NVDA stops speaking no matter what you do and you must close and run it again?
 
Gene

----- Original message -----
From: Don H
Sent: Monday, September 03, 2018 8:42 PM
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Ribbon disabler and more.

George McCoy <slr1bpz@...>
 

I got and mastered Gene's tutorial when I first upgraded to windows 7 back in 2011.  The material still  applies in windows 10.


George

On 9/3/2018 3:47 PM, Gene wrote:
Thank you.  I hope many people find it useful.
 
Gene
----- Original Message -----
Sent: Monday, September 03, 2018 3:21 PM
Subject: Re: [nvda] Ribbon disabler and more.

Thanks, Gene. This ribbon tutorial was excellent.
 
Jean with a J
 
From: Gene
Sent: Monday, September 3, 2018 12:48 PM
Subject: Re: [nvda] Ribbon disabler and more.
 
For those who haven't gotten good instruction or instructional material about ribbons, here is a tutorial, not very long, to read and practice with if you wish.  Don't believe all the negative comments about ribbons until you try working with them yourself.  A lot of the negative comments, perhaps most, are the result of people not getting good instruction or good instructional material.
 
Under my signature is the tutorial.  I don't have Windows 10 so I don't discuss the ribbons there but ribbons are ribbons just as menus are menus.  Once you learn to use ribbons, you can use them anywhere. 
 
Gene
 
I'll provide a brief tutorial based on what I wrote years ago of how to work with ribbons. 
 
I've added a little to it here.
 
I don't know how the organization of Windows has changed in Windows 10 but this description should allow you to look through the Windows ribbons, or any other ribbons, and see how things are organized. 
 
First, I'll discuss a structure found in later versions of Windows that you need to know about-- the split button. 
One thing you will see as you look around ribbons and in other places in Windows are split buttons. A split button often allows you to see more options than just the default action.  Let's take an example. 
Let's say you come across a split button that says shut down Windows.  If you press enter on that button, Windows will shut down.  That is the default action.  Split buttons often show more options if you either right arrow while on the button or down arrow.  As an example, if you are on the shut down split button, you can right arrow and a list of options will open.  the items in the list include sleep, hibernate, restart, and others.  You up or down arrow through the list or use the short cut commands you hear announced as you move through the list.  the letter shortcuts often take actions without pressing enter so be careful when using them, just as you are in menus. 
 
So, let's review.  You find a split button that says shut down.  If you press enter, the computer will shut down. If you right arrow, other options may be displayed.  Or if you down arrow, other options may be displayed.  A split button won't work with both methods.  One method, either right arrowing or down arrowing will do so if it can be done with the button.  Try both methods if you don't know which one might work.  If you are on a tool bar which extends across the screen from left to right, down arrowing will open additional options.  If you think about this, it makes sense.  If you are in a menu, down arrowing will move you to the next item in the menu.  So you right arrow on the split button to cause it to display more options.  In a tool bar that extends across the screen from left to right, right arrowing will move you to the next item in the tool bar.  So you down arrow when on the split button to cause it to display more options.  But some tool bars run up and down the screen, as menus do.  And at times, you may not be sure which way a structure extends on screen.  So, as I said, if you are not sure or don't know, try both methods of causing the split button to display more options.  Often, one of them will work. If you open the options a split button offers and don't want to work with them, arrow in the opposite direction to move out of them.  For example, if you right arrowed to open more options, left arrow. 
Some split buttons don't do anything when you right arrow or down arrow.  In that case, open them with alt down arrow.  Then tab through the additional options.  I've almost never worked in this way with split buttons but if you want to close a split button, try alt up arrow if you've used alt down arrow to open it.
 
Now, to ribbons themselves.
 
Regarding ribbons, much of the complaining about them is not warranted if you understand how they work and how to use short cut commands effectively and efficiently.  and I would strongly recommend against using the JAWS virtual menus, no matter what the JAWS training material says about ribbons being difficult to use.  the training material is just plain wrong and using virtual menus, you will be unnecessarily dependent on one screen-reader.  There are other disadvantages to using them which I won't go into here.
 
Try looking at ribbons and doing what is described below in wordpad.  Everyone with Windows 7 has Wordpad on their machine.  Wordpad provides a good environment to look at and practice working with ribbons.  
 
The essence of working with ribbons is this:
Press alt to move to the upper ribbon.
You will probably be on an item that says home tab. Items on the upper ribbon are announced as tabs such as home tab, view tab, etc. 
To see what ribbons are available, right or left arrow repeatedly to move through the ribbons.  Move in one
direction to move through all of them, just as you would to move through all the menus.
 
For this demonstration, just so we are all doing the same thing, move with the right arrow. When you get back to where you started, you can keep right arrowing to move through the items again, if you wish.  You can move through all the items as many times as you want. Or you can move with the left arrow whenever you want to move in the opposite direction.  
 
Stop on view.  Then start tabbing.  You will move through all items in what is called the lower ribbon that are in the view ribbon. 
 
In other words you tab to see the items in a ribbon once you move to it.  Tab moves you forward through the items, shift tab moves you backword.
So tab and shift tab are used instead of up and down arrow. 
 
Many items in the lower ribbon are buttons.  Use either the space bar or enter to activate the button. You may find a button that opens a menu and if you press enter or the space bar, you will then be in a menu.
 
Each time you move to an item, you will hear the short cut command to work with that item. 
But JAWS has a bug and you often won't.  To hear the short cut, use the command JAWS key tab.  If you are using the default JAWS key, it is either insert.
 
Try tabbing to an item in a Wordpad ribbon and using the command insert tab.  You will hear some extraneous information.  The last thing you will hear is the short cut sequence.  You can repeat the information by repeating the command as often as you want.
 
Let's look at an item which is usually called the application menu.  Return to the main program window in wordpad by closing the ribbons.  You can either press escape repeatedly, if necessary, or you can press alt once.  Now, open the ribbons again with alt. 
Start right arrowing until you get to the application menu.
You will hear application menu and then something like button drop down grid.  Never mind drop down grid.  It's a description you don't have to worry about.  The important things are that you are on a button and at the application menu.  Press enter or the space bar to activate the button.  Activating the button opens the menu.  Start down arrowing. you will hear all the short cut commands necessary to open an item or take an action.  When you got to the menu item, you heard alt f.  When you open the menu and move through it, you will hear all the letters announced.  for example, if you down arrow to save as, you will hear alt f a.  that means that, when you are in the main program window, you open the menu as you always did, alt f, then type a.  Alt f opens the menau and a then opens save as.  Ribbon programs have one menu and you should look through it.  Many important and common commands and interfaces such as options may be there.  By options, I mean the kind of options interface you used to find in the tools menu.
 
Now the we have seen the menu, let's look at the ribbons structure some more.
To review, and add more information, as you have seen, you can move to the ribbon interface with alt.  Then right and left arrow, just as you would move from menu to menu. 
You can also move to a ribbon using alt and a letter.  So, alt h takes you to the home ribbon.  Alt v takes you to the view ribbon, etc.  Once you are on the ribbon you want to work with, tab to move forward through the items in a ribbon.  Shift tab to move back through the items.  So tab and shift tab are used instead of up and down arrow.
Ribbons are divided into categories which you will hear announced as you tab.  for example, in an e-mail program, a ribbon may have a category named respond.  You may hear this announced as respond tool bar.  As you tab, you will hear commands such as reply and forward in the respond category.  When you hear a category announced, don't tab until you hear everything spoken.  You will miss the first command in the category if you do.  I'm talking about working with an unfamiliar ribbon. 
there are often many more commands and items in a ribbon than in a menu.  So memorize command sequences for items you know you will use regularly. 
As I said, there are different categories in ribbons to help organize items.  You can quickly jump from category to category in a ribbon to help you see if there is a category you want to look through. 
Move to a ribbon in Wordpad.  For example, alt h for hhome or alt v for view.
Then repeatedly issue the command control right arrow to move forward from category to category and control left arrow to move back.  When you get to a category you want to hear the items in, start tabbing.  Of course, you can shift tab to move back. 
 
Open a ribbon in Wordpad and tab through it to see how it is organized by moving through it. 
Then use control right arrow to move by category and tab to see what is in a category. 
 
Commands such as control o, control n, control s, control r, etc. are mostly retained in programs
that use ribbons, though you won't hear them announced. If you don't already know them, you'll have to find them in ways such as by looking at a list of keyboard commands for the program.  Such lists are often available in the help for the program. If you already know the commands from having used an older version of the program, most or perhaps even all of the commands you know will work.  


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Quentin Christensen
 

Using either 2018.3beta3, or the latest alpha, I get unknown reported as soon as I close system information, and yes, as soon as I press the windows key, or windows+m etc, I get to the start menu or desktop as expected.  I'm not getting any crash or even an error or warning like the original poster however.

I wonder if the crash is caused by the same action with a differently configured PC, or whether it is something else which is happening around the same time (an example might be changing configuration profiles if there was a triggered one for system information, or an addon which was triggered or looking for something else).



On Tue, Sep 4, 2018 at 11:42 AM, Don H <lmddh50@...> wrote:

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Can one selectively cut and past text from a wordd graphic identifier without the graphic?

Jonathan COHN
 

Use speech history tool?

On 9/1/18, 6:19 AM, "nvda@nvda.groups.io on behalf of Brian's Mail list account via Groups.Io" <nvda@nvda.groups.io on behalf of bglists=blueyonder.co.uk@groups.io> wrote:

So I have a .docx file, when loaded into word, I can hear a description of
the graphic. What I would like to do is cut the description but not the
actual graphic and put it and the text of the document into a text editor.
It seems not to be possible. Selecting the graphic tries to paste it all,
which of course fails. using object nav and the click three times to go to
clipboard does not work either. Am I being thick here?
Short of copying it by typing it, and its quite long there seems to be no
way to get at this description but somebody put it in, one assumes so I'd
have thought emulating what they did, should reveal it.
How?
Brian

bglists@...
Sent via blueyonder.
Please address personal E-mail to:-
briang1@..., putting 'Brian Gaff'
in the display name field.


Re: NVDA, latest alpha works much better in Win10 mail app!

hurrikennyandopo ...
 

Hi David

 

It might be a good idea to do a reset on nvda back to factory defaults. Then make sure you close it then open it again so you get the messages when you install it for the first time.

 

I am still getting no repeats of the letters or lines etc in mail app and I can read back letter by letter word by word etc when replying to a email. I also wonder if when I think it is leno said he can not do letter by letter it is his version of windows? I know in earlier versions of windows when you replied that problem was there but not now. I am on window 10 ver 1803.

 

Gene nz

 

Sent from Mail for Windows 10

 


From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Lino Morales <linomorales001@...>
Sent: Tuesday, September 4, 2018 12:35:36 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA, latest alpha works much better in Win10 mail app!
 

David. You posted about this when was it last week? I don’t understand what your problem was. The only problem I’v had with Mail is when I reply to a message NVDA doesn’t read out what I’m typing. When I read messages I just simply use say all with NVDA plus down arrow.

 

Sent from Mail for Windows 10

 


From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of David Moore <jesusloves1966@...>
Sent: Monday, September 3, 2018 8:32:19 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA, latest alpha works much better in Win10 mail app!
 

Hi all!

I can’t believe what the newest Window Apps Essential’s did for the Win10 Mail app.

I have been hearing the same line repeat as I arrow down through my messages that I am about to send. I am using latest alpha version. I still have a little trouble navigating letter by letter; it says the same letter a few times, but it is so much better!

I could not make corrections at all, because I could not navigate character by character or word by word.

It is all fixed now, and I am so glad!

Do any of you notice a change in how the Win10 Mail app works?

Take care, guys!

David Moore

 

Sent from Mail for Windows 10

 


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Don H
 

Just tried to duplicate this.  Indeed after closing the system information with alt f4 it seems that NVDA goes silent.  after the alt f4 is pressed Nvda says unknown.  Sighted help says I am back to the desktop and nothing is shown besides my normal desktop.     However if you hit windows key m speech returns.  Seems that something is open that is minimized by windows key m. 

On 9/3/2018 7:56 PM, Quentin Christensen wrote:
Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Jason White
 

Thanks – I’ll try to reproduce and to capture debug-level logs.

 

At this point, unfortunately, it will probably have to be tomorrow.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Sent: Monday, September 3, 2018 8:01 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA 2018.3 beta 3 hangs after closing System Information application

 

Hi Jason,

 

It isn't reproducing for me, although I'm using a fast insider build of Windows here.

 

Two things to try:


- If you restart NVDA with add-ons disabled (press NVDA+Q then down arrow to "restart with addons disabled" and press ENTER), does it still happen?

 

- Particularly if the crash doesn't happen with add-ons disabled, make sure you are using the most up to date version of all your addons.  There is also an addon to check that: https://addons.nvda-project.org/addons/addonUpdater.en.html

 

In any case, if you could send me a copy of your full NVDA log, ideally at log level debug, I can have a closer look at what is happening.


Kind regards

 

Quentin.

 

On Tue, Sep 4, 2018 at 5:08 AM, Jason White via Groups.Io <jason@...> wrote:

After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.

 

The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.

 

WARNING - watchdog._watcher (14:47:55.289):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 954, in findGroupboxObject

  File "winUser.pyo", line 430, in getClassName

 

WARNING - watchdog._watcher (14:48:10.339):

Core frozen in stack:

  File "nvda.pyw", line 214, in <module>

  File "core.pyo", line 495, in main

  File "wx\core.pyo", line 2134, in MainLoop

  File "gui\__init__.pyo", line 963, in Notify

  File "core.pyo", line 466, in run

  File "queueHandler.pyo", line 83, in pumpAll

  File "queueHandler.pyo", line 50, in flushQueue

  File "eventHandler.pyo", line 62, in _queueEventCallback

  File "eventHandler.pyo", line 147, in executeEvent

  File "eventHandler.pyo", line 160, in doPreGainFocus

  File "api.pyo", line 107, in setFocusObject

  File "baseObject.pyo", line 34, in __get__

  File "baseObject.pyo", line 115, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container

  File "IAccessibleHandler.pyo", line 945, in findGroupboxObject

  File "winUser.pyo", line 429, in getClassName

 



 

--

Quentin Christensen
Training and Support Manager

 

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

 

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: useing the o c r adon on windows7, is it possable?

Adel Spence
 


thankyou.

----- Original Message -----
Sent: Monday, September 03, 2018 8:42 PM
Subject: Re: [nvda] useing the o c r adon on windows7, is it possable?

Hi Adel,

Yes you should be able to use the OCR addon in Windows 7.  You can either get it by going to the NVDA menu, then tools then Manage add-ons then the "Get add-ons" button, or from: https://addons.nvda-project.org/index.en.html

The OCR add-on is available from this page: https://addons.nvda-project.org/addons/ocr.en.html

Essentially, once setup, move to the image or PDF file (open the PDF file in Adobe reader), etc, then press NVDA+r.  From there use the review cursor to read or copy the text which was found and press escape when done.

All the review cursor keyboard shortcuts are available from the User Guide: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ReviewingText

Alternatively they are in the Basic Training for NVDA module, which also has in-depth step by step activities to help you get familiar with them (not directly with OCR though).  The good news is that the section on the review cursor is in the free sample available from: 

(Electronic text, the sample is a web page link): https://www.nvaccess.org/product/basic-training-for-nvda-ebook/
(Audio, the sample is a single MP3 which will play in your browser or you can download it.  The full course is completely marked up with DAISY): https://www.nvaccess.org/product/basic-training-for-nvda-downloadable-audio/

Regards

Quentin.

On Tue, Sep 4, 2018 at 7:19 AM, Adel Spence <adelspence12@...> wrote:
hi. if I can useing the nvda o c r adin for windows7 please tell me and thanks




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: NVDA 2018.3 beta 3 hangs after closing System Information application

Quentin Christensen
 

Takuya,

Do you have any (other) addons installed, and if so, have you tried restarting with add-ons disabled?  If so, have you checked that you are using the most up to date version of any addons?

And finally, just to check, does this happen immediately after updating either NVDA or Windows, and if so, does it persist after rebooting the computer?

If you also could send me a copy of your full log, ideally at Debug level, I can have a look as well.

I forgot to mention previously, but more information on the log is available at: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps


Kind regards

Quentin.





On Tue, Sep 4, 2018 at 10:01 AM, Takuya Nishimoto <nishimotz@...> wrote:
I have reported regarding similar issue.

https://github.com/nvaccess/nvda/issues/8434

It was difficult to reproduce on other machines than the specific environment.

--
Takuya Nishimoto
nishimotz@...

2018年9月4日(火) 4:08 Jason White via Groups.Io <jason=jasonjgw.net@groups.io>:
>
> After using System Information on Windows 10 1803 (all up to date), and closing the application with Alt+F4, I experienced a hang in NVDA 2018.3 beta 3.
>
>
>
> The log file in my local temporary directory contains the following. Please let me know whether further details are desired, or whether it has been or should be taken up in GitHub.
>
>
>
> WARNING - watchdog._watcher (14:47:55.289):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 954, in findGroupboxObject
>
>   File "winUser.pyo", line 430, in getClassName
>
>
>
> WARNING - watchdog._watcher (14:48:10.339):
>
> Core frozen in stack:
>
>   File "nvda.pyw", line 214, in <module>
>
>   File "core.pyo", line 495, in main
>
>   File "wx\core.pyo", line 2134, in MainLoop
>
>   File "gui\__init__.pyo", line 963, in Notify
>
>   File "core.pyo", line 466, in run
>
>   File "queueHandler.pyo", line 83, in pumpAll
>
>   File "queueHandler.pyo", line 50, in flushQueue
>
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>
>   File "eventHandler.pyo", line 147, in executeEvent
>
>   File "eventHandler.pyo", line 160, in doPreGainFocus
>
>   File "api.pyo", line 107, in setFocusObject
>
>   File "baseObject.pyo", line 34, in __get__
>
>   File "baseObject.pyo", line 115, in _getPropertyViaCache
>
>   File "NVDAObjects\IAccessible\__init__.pyo", line 1579, in _get_container
>
>   File "IAccessibleHandler.pyo", line 945, in findGroupboxObject
>
>   File "winUser.pyo", line 429, in getClassName
>
>
>
>






--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: useing the o c r adon on windows7, is it possable?

Quentin Christensen
 

Hi Adel,

Yes you should be able to use the OCR addon in Windows 7.  You can either get it by going to the NVDA menu, then tools then Manage add-ons then the "Get add-ons" button, or from: https://addons.nvda-project.org/index.en.html

The OCR add-on is available from this page: https://addons.nvda-project.org/addons/ocr.en.html

Essentially, once setup, move to the image or PDF file (open the PDF file in Adobe reader), etc, then press NVDA+r.  From there use the review cursor to read or copy the text which was found and press escape when done.

All the review cursor keyboard shortcuts are available from the User Guide: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ReviewingText

Alternatively they are in the Basic Training for NVDA module, which also has in-depth step by step activities to help you get familiar with them (not directly with OCR though).  The good news is that the section on the review cursor is in the free sample available from: 

(Electronic text, the sample is a web page link): https://www.nvaccess.org/product/basic-training-for-nvda-ebook/
(Audio, the sample is a single MP3 which will play in your browser or you can download it.  The full course is completely marked up with DAISY): https://www.nvaccess.org/product/basic-training-for-nvda-downloadable-audio/

Regards

Quentin.

On Tue, Sep 4, 2018 at 7:19 AM, Adel Spence <adelspence12@...> wrote:
hi. if I can useing the nvda o c r adin for windows7 please tell me and thanks




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Multi language support

Quentin Christensen
 

Hi Cristóbal,

In NVDA's voice / speech settings (press NVDA+control+v to open directly or from the NVDA menu, then preferences, then settings, then speech) are options for language.

After selecting the synthesizer to use, you can choose the voice and possibly variant.  Different synths work differently - some use voice and variant, some only have voice, some have different languages (or really it's how different sounds are pronounced so that it sounds correct in the particular language).

There are also options for automatic language and dialect switching when supported.

If a web page or document etc is setup correctly, it will identify what language it is written in, and in that case, NVDA is able to switch to the correct language automatically.

Otherwise, you can use configuration profiles to switch languages, and you can either have it setup so that it switches based on the program in use, or manually.

There is some information on configuration profiles in the User Guide: https://www.nvaccess.org/files/nvda/documentation/userGuide.html#ConfigurationProfiles 

Alternatively, it is covered in detail in the Basic Training for NVDA module, available from: http://www.nvaccess.org/shop/

Kind regards

Quentin



On Tue, Sep 4, 2018 at 7:10 AM, Cristóbal <cristobalmuli@...> wrote:

Hello list,

I’m mainly a Jaws user, but fall back on NVDA for this or that reason from time to time. I’m therefore not as well versed in some aspects of the screen reader. I am thus unfamiliar with NVDA multilanguage support.

In my case, it would be American English and Mexican/Latin American Spanish from German from time to time.

Where or how does one go about enabling language switching in NVDA? Be it on the fly or to create different voice profiles and whatnot?

 

Thanks,

Cristóbal




--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess