|
Re: Windows 10 Essentials Error on Stable Channel
Hi,
toggle quoted messageShow quoted text
I see. Which version of Windows 10 App Essentials do you have? Technical: the regular expression used to locate version metadata isn't working for this user. If one is using 18.05.x series, chances are that the URL for the add-on download package isn't recognized. I'll do something about this for 18.09 release (around Labor Day weekend in the United States). Prior to that, one workaround is to visit the add-ons website and download the latest stable version (18.08.1). Cheers, Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Richard Wells Sent: Monday, August 13, 2018 12:38 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 Essentials Error on Stable Channel Here ya go Joseph! INFO - __main__ (13:48:23.391): Starting NVDA INFO - core.main (13:48:23.642): Config dir: C:\Users\richw\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:48:23.642): Loading config: C:\Users\richw\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:48:23.674): NVDA version 2018.2.1 INFO - core.main (13:48:23.674): Using Windows version 10.0.17134 workstation INFO - core.main (13:48:23.674): Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:48:23.674): Using comtypes version 1.1.3 INFO - synthDriverHandler.setSynth (13:48:24.676): Loaded synthDriver eloquence INFO - core.main (13:48:24.676): Using wx version 3.0.2.0 msw (classic) INFO - brailleInput.initialize (13:48:24.676): Braille input initialized INFO - braille.initialize (13:48:24.676): Using liblouis version 3.5.0 ERROR - braille.BrailleHandler.setDisplayByName (13:48:24.686): Error initializing display driver Traceback (most recent call last): File "braille.pyo", line 1595, in setDisplayByName File "brailleDisplayDrivers\baum.pyo", line 223, in __init__ RuntimeError: No Baum display found INFO - braille.BrailleHandler.setDisplayByName (13:48:24.686): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:48:24.776): UIAutomation: IUIAutomation5 INFO - core.main (13:48:25.671): NVDA initialized ERROR - external:globalPlugins.wintenObjs.w10config.addonUpdateCheck (13:48:36.786): Error checking for update Traceback (most recent call last): File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 111, in addonUpdateCheck File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 101, in checkForAddonUpdate AttributeError: 'NoneType' object has no attribute 'groupdict' ERROR - external:globalPlugins.wintenObjs.w10config.addonUpdateCheck (14:37:44.476): Error checking for update Traceback (most recent call last): File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 111, in addonUpdateCheck File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 101, in checkForAddonUpdate AttributeError: 'NoneType' object has no attribute 'groupdict' INFO - inputCore.InputManager._handleInputHelp (14:37:52.584): Input help: gesture kb(desktop):NVDA INFO - inputCore.InputManager._handleInputHelp (14:37:52.740): Input help: gesture kb(desktop):NVDA+1, bound to script toggleInputHelp on globalCommands.GlobalCommands INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:37:54.292): Developer info for navigator object: name: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel' role: ROLE_DOCUMENT states: STATE_READONLY, STATE_FOCUSABLE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_BrokenFocusedStateDocumentMozillaIAccessible object at 0x051A48B0> Python class mro: (<class 'NVDAObjects.Dynamic_BrokenFocusedStateDocumentMozillaIAccessible'>, <class 'NVDAObjects.IAccessible.mozilla.BrokenFocusedState'>, <class 'NVDAObjects.IAccessible.mozilla.Document'>, <class 'NVDAObjects.IAccessible.mozilla.Mozilla'>, <class 'NVDAObjects.IAccessible.ia2Web.Document'>, <class 'NVDAObjects.IAccessible.ia2Web.Ia2Web'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: u'' location: (0, 195, 1894, 792) value: None appModule: <'thunderbird' (appName u'thunderbird', process ID 10968) at address 50301f0> appModule.productName: u'Thunderbird' appModule.productVersion: u'52.9.1' TextInfo: <class 'NVDAObjects.IAccessible.IA2TextTextInfo'> windowHandle: 1704946L windowClassName: u'MozillaWindowClass' windowControlID: 0 windowStyle: 399441920 windowThreadID: 10832 windowText: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel - Inbox - richwels@... - Mozilla Thunderbird' displayText: u'' IAccessibleObject: <POINTER(IAccessible2) ptr=0x6c105c at 52a14e0> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=1704946, objectID=-4, childID=-2012 IAccessible accName: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel' IAccessible accRole: ROLE_SYSTEM_DOCUMENT IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048644) IAccessible accDescription: u'' IAccessible accValue: u'imap://richwels%40gmx%2Ecom@...:993/fetch%3EUID%3E/INBOX%3E6006' IAccessible2 windowHandle: 1704946 IAccessible2 uniqueID: -2012 IAccessible2 role: ROLE_SYSTEM_DOCUMENT IAccessible2 states: IA2_STATE_OPAQUE (1024) IAccessible2 attributes: u'margin-left:8px;text-align:start;text-indent:0px;margin-right:8px;tag:body;margin-top:8px;margin-bottom:8px;display:block;explicit-name:true;' On 8/13/2018 9:55 AM, Joseph Lee wrote: Hi,
|
|
|
|
Re: Windows 10 Essentials Error on Stable Channel
Richard Wells
Here ya go Joseph!
toggle quoted messageShow quoted text
INFO - __main__ (13:48:23.391): Starting NVDA INFO - core.main (13:48:23.642): Config dir: C:\Users\richw\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:48:23.642): Loading config: C:\Users\richw\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:48:23.674): NVDA version 2018.2.1 INFO - core.main (13:48:23.674): Using Windows version 10.0.17134 workstation INFO - core.main (13:48:23.674): Using Python version 2.7.15 (v2.7.15:ca079a3ea3, Apr 30 2018, 16:22:17) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:48:23.674): Using comtypes version 1.1.3 INFO - synthDriverHandler.setSynth (13:48:24.676): Loaded synthDriver eloquence INFO - core.main (13:48:24.676): Using wx version 3.0.2.0 msw (classic) INFO - brailleInput.initialize (13:48:24.676): Braille input initialized INFO - braille.initialize (13:48:24.676): Using liblouis version 3.5.0 ERROR - braille.BrailleHandler.setDisplayByName (13:48:24.686): Error initializing display driver Traceback (most recent call last): File "braille.pyo", line 1595, in setDisplayByName File "brailleDisplayDrivers\baum.pyo", line 223, in __init__ RuntimeError: No Baum display found INFO - braille.BrailleHandler.setDisplayByName (13:48:24.686): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:48:24.776): UIAutomation: IUIAutomation5 INFO - core.main (13:48:25.671): NVDA initialized ERROR - external:globalPlugins.wintenObjs.w10config.addonUpdateCheck (13:48:36.786): Error checking for update Traceback (most recent call last): File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 111, in addonUpdateCheck File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 101, in checkForAddonUpdate AttributeError: 'NoneType' object has no attribute 'groupdict' ERROR - external:globalPlugins.wintenObjs.w10config.addonUpdateCheck (14:37:44.476): Error checking for update Traceback (most recent call last): File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 111, in addonUpdateCheck File "C:\Users\richw\AppData\Roaming\nvda\addons\wintenApps\globalPlugins\wintenObjs\w10config.py", line 101, in checkForAddonUpdate AttributeError: 'NoneType' object has no attribute 'groupdict' INFO - inputCore.InputManager._handleInputHelp (14:37:52.584): Input help: gesture kb(desktop):NVDA INFO - inputCore.InputManager._handleInputHelp (14:37:52.740): Input help: gesture kb(desktop):NVDA+1, bound to script toggleInputHelp on globalCommands.GlobalCommands INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (14:37:54.292): Developer info for navigator object: name: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel' role: ROLE_DOCUMENT states: STATE_READONLY, STATE_FOCUSABLE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_BrokenFocusedStateDocumentMozillaIAccessible object at 0x051A48B0> Python class mro: (<class 'NVDAObjects.Dynamic_BrokenFocusedStateDocumentMozillaIAccessible'>, <class 'NVDAObjects.IAccessible.mozilla.BrokenFocusedState'>, <class 'NVDAObjects.IAccessible.mozilla.Document'>, <class 'NVDAObjects.IAccessible.mozilla.Mozilla'>, <class 'NVDAObjects.IAccessible.ia2Web.Document'>, <class 'NVDAObjects.IAccessible.ia2Web.Ia2Web'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: u'' location: (0, 195, 1894, 792) value: None appModule: <'thunderbird' (appName u'thunderbird', process ID 10968) at address 50301f0> appModule.productName: u'Thunderbird' appModule.productVersion: u'52.9.1' TextInfo: <class 'NVDAObjects.IAccessible.IA2TextTextInfo'> windowHandle: 1704946L windowClassName: u'MozillaWindowClass' windowControlID: 0 windowStyle: 399441920 windowThreadID: 10832 windowText: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel - Inbox - richwels@... - Mozilla Thunderbird' displayText: u'' IAccessibleObject: <POINTER(IAccessible2) ptr=0x6c105c at 52a14e0> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=1704946, objectID=-4, childID=-2012 IAccessible accName: u'Re: [nvda] Windows 10 Essentials Error on Stable Channel' IAccessible accRole: ROLE_SYSTEM_DOCUMENT IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048644) IAccessible accDescription: u'' IAccessible accValue: u'imap://richwels%40gmx%2Ecom@...:993/fetch%3EUID%3E/INBOX%3E6006' IAccessible2 windowHandle: 1704946 IAccessible2 uniqueID: -2012 IAccessible2 role: ROLE_SYSTEM_DOCUMENT IAccessible2 states: IA2_STATE_OPAQUE (1024) IAccessible2 attributes: u'margin-left:8px;text-align:start;text-indent:0px;margin-right:8px;tag:body;margin-top:8px;margin-bottom:8px;display:block;explicit-name:true;'
On 8/13/2018 9:55 AM, Joseph Lee wrote:
Hi,
|
|
|
|
Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
Gene
Testing using Narrator might not tell you useful
information in this case. I'm sure you can turn off Narrator's start at
bootup option if it is on, but aside from that, my point is that you can test
this problem and still have speech. Test with JAWS and then test with NVDA
or in reverse order if you wish. Or make sure you can, in fact, log in
without speech first by trying it with the screen-reader running and making sure
you know the exact procedure.
Specifics aside, my general point is that you
shouldn't test without speech unless such testing is necessary and that, if you
do so, you should be sure you know how to do necessary actions without speech,
such as in this case, log in. Or you should make sure you can run Narrator
if necessary on the login screen. In other words, something to make sure
you aren't locked out of your computer because you can't log in. When
testing something else, if you need to take a critical action without speech,
you should know exactly how.
Gene
----- Original Message -----
From: Ervin, Glenn
Sent: Monday, August 13, 2018 10:11 AM
Subject: Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on
Windows start-up I would have been worried that invoking Narrator at the login screen would have left Narrator going at subsequent logins, thus causing the same problem. Glenn
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
I'll look at the original message again. but I commented because of this passage in your original message: When I restarted I was then blind” audially! However, I took a chance and typed my password in in the usual way and got back to the desktop in silence.
This sounds as though you didn't know if you could enter your password without speech. for that reason, I tried to think of other ways to test what you were testing. At this point, without looking at the original message again, I'm not sure if my suggestion of how to test fit what you were doing. But my whole point is that if there is a way to test without losing accessibility, unless you are sure you can do something without speech, it is far better to keep accessibility if that means you may not be able to do something critical such as sign in.
Gene ----- Original Message ----- From: Cearbhall O'Meadhra Sent: Saturday, August 11, 2018 11:54 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
Gene,
You are mistaken, if you read my description again, you will see that indeed both the JAWS and the NVDA settings were on. This duplication is what was being tested. The loss of accessibility was a risk, as you rightly say. However, my experience has demonstrated that there is only one edit box in the start-up screen and it was only necessary to put the password in in the usual way that it had been done before to get into the full Windows session.
This could not have been tested if the NVDA switch was left active. The silence itself was the test.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
The point is that the speech on bootup setting in the Ease of Access Center was turned off and the effect of that was being tested. The person booted up without speech and he said that, luckily, he was able to enter his password. What if he hadn't been able to, something he didn't know. If you trouble shoot, if you are testing something that doesn't require a loss of accessibility, you should take steps to retain accessibility. In this case, NVDA could have been told to run at boot up and nothing would have been lost in the trouble shooting that was being done.
The NVDA setting wasn't being tested, it hadn't been on. the incorrect setting for what was desired had been on in the Ease of Access Center. The desired setting could have been turned on with no loss of accessibility and no impairment of the test being done.
Gene ----- Original Message ----- From: Brian Vogel Sent: Saturday, August 11, 2018 9:57 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
On Sat, Aug 11, 2018 at 08:45 AM, Gene wrote:
It strikes me that troubleshooting steps
were being described in detail, not the final and permanent state of
affairs. Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134 A little kindness from person to person is better than a vast love for all humankind. ~ Richard Dehmel
|
|
|
|
Re: How to configure Switch Synth?
Diana Kwok <dkwok2017@...>
Thanks Larry J. I don’t think we’ll go for Vocalizer Expressive just yet… Best, Diana.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Larry Wang
<larry.wang.801@...>
Sent: Monday, August 13, 2018 4:42:32 AM To: nvda@nvda.groups.io Subject: Re: [nvda] How to configure Switch Synth?
Hi Diana, If you use vocalizer expressive , just enable Detect text language based on unicode characters (experimental) check box in Vocalizer Expressive sub Menu -> Automatic Language Switching Settings. Then set voices for English and Chinese ..
On Sun, Aug 12, 2018 at 5:16 PM, Diana Kwok <dkwok2017@...> wrote:
|
|
|
|
Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
Ervin, Glenn
I would have been worried that invoking Narrator at the login screen would have left Narrator going at subsequent logins, thus causing the same problem. Glenn
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Gene
Sent: Saturday, August 11, 2018 12:05 PM To: nvda@nvda.groups.io Subject: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
I'll look at the original message again. but I commented because of this passage in your original message: When I restarted I was then blind” audially! However, I took a chance and typed my password in in the usual way and got back to the desktop in silence.
This sounds as though you didn't know if you could enter your password without speech. for that reason, I tried to think of other ways to test what you were testing. At this point, without looking at the original message again, I'm not sure if my suggestion of how to test fit what you were doing. But my whole point is that if there is a way to test without losing accessibility, unless you are sure you can do something without speech, it is far better to keep accessibility if that means you may not be able to do something critical such as sign in.
Gene ----- Original Message ----- From: Cearbhall O'Meadhra Sent: Saturday, August 11, 2018 11:54 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
Gene,
You are mistaken, if you read my description again, you will see that indeed both the JAWS and the NVDA settings were on. This duplication is what was being tested. The loss of accessibility was a risk, as you rightly say. However, my experience has demonstrated that there is only one edit box in the start-up screen and it was only necessary to put the password in in the usual way that it had been done before to get into the full Windows session.
This could not have been tested if the NVDA switch was left active. The silence itself was the test.
From: nvda@nvda.groups.io <nvda@nvda.groups.io>
On Behalf Of Gene
The point is that the speech on bootup setting in the Ease of Access Center was turned off and the effect of that was being tested. The person booted up without speech and he said that, luckily, he was able to enter his password. What if he hadn't been able to, something he didn't know. If you trouble shoot, if you are testing something that doesn't require a loss of accessibility, you should take steps to retain accessibility. In this case, NVDA could have been told to run at boot up and nothing would have been lost in the trouble shooting that was being done.
The NVDA setting wasn't being tested, it hadn't been on. the incorrect setting for what was desired had been on in the Ease of Access Center. The desired setting could have been turned on with no loss of accessibility and no impairment of the test being done.
Gene ----- Original Message ----- From: Brian Vogel Sent: Saturday, August 11, 2018 9:57 AM Subject: Re: [nvda] Need to speed up Slow voice on Windows start-up
On Sat, Aug 11, 2018 at 08:45 AM, Gene wrote:
It strikes me that troubleshooting steps were being described in detail, not the final and permanent state of affairs. Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134 A little kindness from person to person is better than a vast love for all humankind. ~ Richard Dehmel
|
|
|
|
Re: [nvda-addons] Ping Joseph.
Hi,
toggle quoted messageShow quoted text
I'm thinking the add-on update state file used by this add-on might have become corrupt. I'll try my best to come up with a fix as part of the next release. Cheers, Joseph
-----Original Message-----
From: nvda-addons@nvda-addons.groups.io <nvda-addons@nvda-addons.groups.io> On Behalf Of Brian's Mail list account via Groups.Io Sent: Monday, August 13, 2018 1:40 AM To: nvda-addons@nvda-addons.groups.io; nvda@groups.io Subject: [nvda-addons] Ping Joseph. Hi a number of people on the nvda list myself included have had problems with putting the add on updater on installed copies of the latest beta of nvda. The eof error happens and its as if the add on is not there. However I just set up a portable version of the same snap and it installs there with no issues, likewise on portable versions of alpha and the stable release of nvda. Is there something different about an installed copy, or do we all have some kind of corruption that causes this effect. I've tried changing add ons around but the effect remains the same, so I'm reasonably sure its not an add on that is causing the issue, as now my alpha portable and the beta installed have exactly the same add ons and versions but the installed beta still has the error at start up or install and is thus not working. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field.
|
|
|
|
Re: Windows 10 Essentials Error on Stable Channel
Hi,
toggle quoted messageShow quoted text
When the failure occurs, press NVDA+F1 to open the log viewer. Then copy and paste either the last error traceback paragraph or the entire content (in this case, full content might be helpful). Cheers, Joseph
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Richard Wells Sent: Monday, August 13, 2018 6:25 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 Essentials Error on Stable Channel Joseph: It fails reliably. Where do I get the log? I know this has been covered on this list, but I can't find the thread. On 8/12/2018 9:54 PM, Joseph Lee wrote: Hi,
|
|
|
|
Re: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
Ervin, Glenn
Thanks for notifying the list. It will possibly help someone in the future, when searching for a solution. Messages from a list show up on web searches, which is how I often resolve computer conundrums. Glenn
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of
Cearbhall O'Meadhra
Sent: Saturday, August 11, 2018 5:53 AM To: nvda@nvda.groups.io Subject: [SUSPECT URL!]Re: [nvda] Need to speed up Slow voice on Windows start-up
Chris, Brian, Sarah,
I found the source of the problem!
In the Ease of Access settings I had enabled both Jaws and NVDA to speak on the sign-in screen. JAWS was first, so I suppose it took control of the dialog. I found the miserable voice in the JAWS voice settings where MS SAPI 5 was set to a rate of 50 using David, which turned out to be the very voice that I was searching for. Anyway, there was no point in having two screen readers speak on the sign-in screen so I turned them both off. When I restarted I was then blind” audially! However, I took a chance and typed my password in in the usual way and got back to the desktop in silence. I then went to NVDA and found that the start NVDA in the start-up window was now turned off – I presume that this was as a result of changing the setting in the Ease of Access setting. I enabled NVDA alone at sign-up and now NVDA has control of the start-up screen with Eloquence speaking!
All the best,
Cearbhall
m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...
From: nvda@nvda.groups.io <nvda@nvda.groups.io>
On Behalf Of Brian Vogel
On Fri, Aug 10, 2018 at 01:24 PM, Sarah k Alawami wrote:
You mean Settings, Time & Language, then, depending on what you really intend to do: Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134 A little kindness from person to person is better than a vast love for all humankind. ~ Richard Dehmel
|
|
|
|
Re: The Way NVDA Announces Punctuation As I Type
Gene
You have been talking about what happens when you
type. Now, you appear to be talking about how punctuation is being read
when you actually read text. Aside from differences in typing echo, are
you talking about other differences?
Gene
----- Original Messsage -----
From: Wilco
Sent: Monday, August 13, 2018 8:18 AM
Subject: Re: [nvda] The Way NVDA Announces Punctuation As I
Type Hi All. Thanks for all your help on this. I have a decent understanding of the situation now. As a writer by profession, the way my screenreader speaks to me as I type is really important, so things like the apostrophe issue can really interrupt my workflow and make the sentence I am putting together sound really odd. Likewise, the way the screenreader reads documents in Say All is also pretty crucial since it can make my copy sound really fluid if read well, or conversely, it can make good prose sound terrible if not read properly. I’m trying to get used to how NVDA handles commas at the moment for example, because it does make my work sound completely different to how it does when read with JAWS.
Thanks for all your help though.
|
|
|
|
Re: Windows 10 Essentials Error on Stable Channel
Richard Wells
Joseph: It fails reliably. Where do I get the log? I know this has been covered on this list, but I can't find the thread.
toggle quoted messageShow quoted text
On 8/12/2018 9:54 PM, Joseph Lee wrote:
Hi,
|
|
|
|
Re: The Way NVDA Announces Punctuation As I Type
Wilco
Hi All. Thanks for all your help on this. I have a decent understanding of the situation now. As a writer by profession, the way my screenreader speaks to me as I type is really important, so things like the apostrophe issue can really interrupt my workflow and make the sentence I am putting together sound really odd. Likewise, the way the screenreader reads documents in Say All is also pretty crucial since it can make my copy sound really fluid if read well, or conversely, it can make good prose sound terrible if not read properly. I’m trying to get used to how NVDA handles commas at the moment for example, because it does make my work sound completely different to how it does when read with JAWS.
Thanks for all your help though.
|
|
|
|
Re: List of Annotations in Word
Rick
Hello Quentin:
Thanks for your explanation. I was trying to find a common thread before mentioning this problem. Has it been considered to split the annotations into 2 separate panes, one for only comments and another for insertions and deletions (my preference)? This might make each faster. I think this is how WindowEyes did it in the past. Also, what about producing the partial results after the 20 seconds. Something is often better than nothing. The only issue here is how to announce that the results are incomplete.
Whatever you do, don’t go to the separate keystrokes for each type like in Jaws. I can never remember all the different keystrokes. I like the single dialog with multiple choices.
Also, is there a way to select the default view. While some people might prefer links as the default, since I mainly work with reviewing, I much prefer annotations as the default when first invoking the elements dialog.
Rick
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Quentin Christensen
Hi Kelby,
It is an issue we are aware of. The issue and associated conversation are at: https://github.com/nvaccess/nvda/issues/6297
Basically NVDA gives the process 20 seconds to run and if it hasn't finished in that time, it cancels it so that the user isn't left with an unresponsive system for too long. We're looking into how we can improve that.
Word's reviewing pane lists all the track changes etc. You can get to that from the reviewing pane, and the easy, quick and logical shortcut* to get to it is alt+r, z, t, t, p, enter
If you want to "clear" track changes so you can just see comments etc, you can press ALT+r, a, 2, s to accept all tracked changes and turn off tracking.
*Shortcut may or may not be easy, quick or logical
Quentin.
On Fri, Aug 3, 2018 at 7:09 AM, kelby carlson <kelbycarlson@...> wrote:
-- Quentin Christensen
Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/
Facebook: http://www.facebook.com/NVAccess
|
|
|
|
Re: how to start a connectgion with remote Addon?
Chris Mullins
Hi
toggle quoted messageShow quoted text
Download and install the remote add-on on both your own and your client's machines, then view the attached help file via theManage add-ons dialog. The different methods of connecting are described there. Cheers Chris
-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jaffar Sidek Sent: 13 August 2018 01:38 To: nvda@nvda.groups.io Subject: [nvda] how to start a connectgion with remote Addon? Hi all. I need to be connecting to a client's desktop with NVDA soon. How can I establish the address of the client's computer for me to connect to? Should I ask him to ping his IP address and use that as the cooection or is there another way? Cheers!
|
|
|
|
Re: Screen Curtain August 7th build: to go live in halfanhour, website entry will return at the same time
Nika Tsiklauri
Hello! How to assign the gesture to the screen curtain? thanks, Nick.
|
|
|
|
Re: problem with addon updater
Clare Page <clare.page@...>
Hi ! It isn’t just in alpha and beta snapshots of NVDA that this problem with Add-On Updater occurs: I have had it twice using the latest full version of NVDA, 2018.2.1, on a Windows 7 computer. I had already had that problem when I installed Add-On Updater 18.08.4, but at the time, having read that it was a patch to get rid of a bug in 18.08.3 which I had never installed, I thought maybe skipping versions might be to blame; When I read on this list about the release of Add-On Updater 18.08.5, I did a clean install of that version, and I still don’t have Check For Updates in my NVDA Tools menu, nor anything to do with the add-on updater in my NVDA settings. It’s interesting that only a few of us have this bug. Does this add-on only work for Windows 8 or Windows 10? Or is there something else causing this problem, Thanks in advance for any possible theories in answer to these questions. Bye for now! From Clare
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of David Moore
Sent: dimanche 12 août 2018 10:18 To: nvda@nvda.groups.io Subject: Re: [nvda] problem with addon updater
Yes, I am getting the same results! Updater works great with alpha snapshots, but not with beta! David Moore
Sent from Mail for Windows 10
From: Brian's Mail list account via Groups.Io
I'm in the same position with it on the beta 2 version installed, yet alpha snaps are working as portable and the add on is OK there. Look at the errors I posted on the add ons list. It seems to be the eof error that is doing it. I cannot see any difference between the add ons on both systems, so unless the beta of nvda latest version is somehow different. I have had to turn it off as all I get otherwise is an error on nvda start up and no menu option. Could there be some remnant of something left that its seeing as a file it needs to scan? Brian
bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field. ----- Original Message ----- From: "Joseph Lee" <joseph.lee22590@...> To: <nvda@nvda.groups.io> Sent: Saturday, August 11, 2018 10:46 PM Subject: Re: [nvda] problem with addon updater
> Hi, > > Which NVDA version do you have? If it is 2018.2, chances are that it might > be something going wrong when the add-on starts, or somehow the > installation > has become corrupt. > > Cheers, > > Joseph > > > > From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Darren Harris > via Groups.Io > Sent: Saturday, August 11, 2018 2:29 PM > To: nvda@nvda.groups.io > Subject: [nvda] problem with addon updater > > > > Hi, > > > > I've tried uninstalling and reinstalling addon updater. I can't get the > check for updates option to show up at all. > > > > > > >
|
|
|
|
Ping Joseph.
Brian's Mail list account
Hi a number of people on the nvda list myself included have had problems with putting the add on updater on installed copies of the latest beta of nvda. The eof error happens and its as if the add on is not there.
However I just set up a portable version of the same snap and it installs there with no issues, likewise on portable versions of alpha and the stable release of nvda. Is there something different about an installed copy, or do we all have some kind of corruption that causes this effect. I've tried changing add ons around but the effect remains the same, so I'm reasonably sure its not an add on that is causing the issue, as now my alpha portable and the beta installed have exactly the same add ons and versions but the installed beta still has the error at start up or install and is thus not working. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field.
|
|
|
|
Re: how to start a connectgion with remote Addon?
Brian's Mail list account
They are talking about the add on for nvda called nvda remote which is directly for the purpose of interconnecting two computers with nvda on them.
toggle quoted messageShow quoted text
Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field.
----- Original Message -----
From: "Diana Kwok" <dkwok2017@...> To: <nvda@nvda.groups.io> Sent: Monday, August 13, 2018 6:43 AM Subject: Re: [nvda] how to start a connectgion with remote Addon? Hi, How about TeamViewer? However, I'm not sure how it would work with NVDA. Cheers, Diana. ________________________________ From: nvda@nvda.groups.io <nvda@nvda.groups.io> on behalf of Richard Wells <richwels@...> Sent: Monday, August 13, 2018 9:18:30 AM To: nvda@nvda.groups.io Subject: Re: [nvda] how to start a connectgion with remote Addon? It is better for both of you to connect to nvdaremote.com and choose your pass key either manually or letting the server choose one. On 8/12/2018 7:38 PM, Jaffar Sidek wrote: Hi all. I need to be connecting to a client's desktop with NVDA soon.
|
|
|
|
Re: how to start a connectgion with remote Addon?
Brian's Mail list account
Yes its secure this way. Not done it lately myself though.
toggle quoted messageShow quoted text
Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field.
----- Original Message -----
From: "Richard Wells" <richwels@...> To: <nvda@nvda.groups.io> Sent: Monday, August 13, 2018 2:18 AM Subject: Re: [nvda] how to start a connectgion with remote Addon? It is better for both of you to connect to nvdaremote.com and choose your pass key either manually or letting the server choose one.
|
|
|
|
Re: Help w/a log fragment, please
Brian's Mail list account
OK since we do not know what the actual effect of this was other than a slugging of the nvda operation, and do not know hat it was, its a bit hard to comment, but that has never stopped me before!
toggle quoted messageShow quoted text
Seriously, though, in case others do have this, it would be nice if you told the masses for anyone else in the future to learn from. Brian bglists@... Sent via blueyonder. Please address personal E-mail to:- briang1@..., putting 'Brian Gaff' in the display name field.
----- Original Message -----
From: "Jackie" <abletec@...> To: "nvda" <nvda@nvda.groups.io> Sent: Sunday, August 12, 2018 11:20 PM Subject: Re: [nvda] Help w/a log fragment, please Well, never mind. I think I see what the problem is, though I'm not sure how it happened. On 8/12/18, Jackie <abletec@...> wrote: I know something's amiss here, but I am uncertain as to what. Any -- Remember! Friends Help Friends Be Cybersafe Jackie McBride Helping Cybercrime Victims 1 Person at a Time https://brighter-vision.com
|
|
|
|
Re: Microsoft Word 2016 stop working.
Daniele Casarola
Thank you Pranav for your reply.
It was a test tried together with Microsoft Office support, but both hardware acceleration active or not, the problem appears anyway. This is the graphic card installed on the desktop pc: MSI GeForce GTX 1050 Ti 4GB aero Itx Ocv1
|
|
|