|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Mike Capelle <mcap@...>
Thanks so much for this.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Sunday, December 1, 2019 12:53 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi, NVDA 2019.3 stable version is not available yet, but the alpha snapshots are (I don’t recommend using alpha builds unless you are ready to provide feedback or deal with bleeding-edge code). The message about add-ons might be due to you checking for development releases. I’ll make a general community announcement about it in the coming hours. Cheers, Joseph From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mike Capelle
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
|
|
Community add-ons and NVDA 2019.3 update: live development snapshots
Hi NVDA users,
As some of you may have noticed, certain builds of various community add-ons will advertise themselves as compatible with or requiring NVDA 2019.3 in any form. This is because several of us are releasing live development snapshots to test how add-ons are doing in the real world. This is typically done via development snapshots, but I know that some stable releases do contain code that will function in old and new NVDA releases.
Answers to some frequently asked questions:
Q. When I try to install an add-on, NVDA says “minimum version: 2019.3”.
Some add-ons (especially recent development snapshots) do require NVDA 2019.3 as they utilize code introduced in this release (not just Python 3).
Q. I have 2019.3 alpha and an add-on update says it is not compatible.
At least one add-on is retiring (or is end of life) as features from it are part of NVDA.
Q. I’m using Add-on Updater. I recently updated to a dev version yet Add-on Updater wants to download an old release.
This is due to add-on files database records. If you run into this, disable update check for affected add-ons (NVDA menu/Preferences/Settings/Add-on Updater/Do not update add-ons list and check ones you don’t want to get updates).
Q. I’m using NVDA 2019.2.1 with Add-on Updater installed, and when I check for updates, I get an update that isn’t compatible with the version I’m using.
You need to switch to stable channel for the time being (NVDA menu/Preferences/Settings/Add-on Updater/Prefer development releases, uncheck add-ons that you wish to switch to stable channel).
Q. What if my add-on is not listed n Add-on Updater?
Not all add-on updates can be checked via Add-on Updater (many speech synthesizers are excluded form update checks). The best course of action is contacting add-on authors about compatibility of these add-ons.
Q. I wish to report compatibility status of some add-ons.
Please do so if and only if you have absolutely latest releases and you are confident that the add-on in question is indeed incompatible in some way.
For people using my add-ons: for people using development snapshots of various add-ons, recent and upcoming snapshots will require NVDA 2019.3 in order to function. This is done to test how my add-ons are doing in the real world, and only after going through testing will they graduate to stable channel (this will happen after 2019.3 beta or RC is released).
Cheers, Joseph
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Hi, NVDA 2019.3 stable version is not available yet, but the alpha snapshots are (I don’t recommend using alpha builds unless you are ready to provide feedback or deal with bleeding-edge code). The message about add-ons might be due to you checking for development releases. I’ll make a general community announcement about it in the coming hours. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mike Capelle
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
On Sun, Dec 1, 2019 at 01:50 PM, Mike Capelle wrote:
Where do I get 19.3 of NVDA?The latest released version of NVDA is 2019.2.1. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Mike Capelle <mcap@...>
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
|
|
Re: Typhoon
Rosemarie Chavarria
I'll be praying for you too. I've heard those typhoons are really awful.
toggle quoted messageShow quoted text
On 12/1/2019 5:18 AM, molly the blind tech lover wrote:
I will be praying for you. God bless you and your family.
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Gary Metzler
toggle quoted messageShow quoted text
From: Joseph Lee
Sent: Sunday, December 1, 2019 10:30 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi, Glad it is resolved for you. Let us know if you run into other issues in the future. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a reset of my windows and now I get the right version number. Thanks for all your help.
Sent from Mail for Windows 10
From: Joseph Lee
Hi, Try going to addons.nvda-project.org. I think this issue is way beyond add-ons – it is NVDA compatibility mode problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
For some reason I can’t get to the nvda add on page. I want to show the ms tech the problem I am having How can I get to the add on page? Thanks for any help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Complete reset as in performing a Windows 10 reset with no user data left. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Hi, At this point, I’m out of options except for a complete reset. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a repair last night but,it didn’t help. Thanks for all your help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, this confirms the suspicion that somehow NVDA is told to run in compatibility mode when installed. If removing and reinstalling NVDA from scratch (including via portable copy) doesn’t work, chances are that this might be a registry issue that is way beyond our control. The most effective way to resolve this (apart from changing compatibility mode settings, which might be something not many people are familiar with) is a non-destructive Windows 10 reinstall using Media Creation Tool for Version 1909. Failing that, a reset might be in order (you must reinstall desktop apps including NVDA if you decide to go down this path). Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I ran the portable copy and installed from there but, I still get version 8 .
Here is the log:
INFO - __main__ (15:33:23.819): Starting NVDA INFO - core.main (15:33:24.457): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:33:24.457): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:33:24.829): NVDA version 2019.2.1 INFO - core.main (15:33:24.829): Using Windows version 6.2.9200 workstation INFO - core.main (15:33:24.829): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:33:24.829): Using comtypes version 1.1.7 INFO - core.main (15:33:24.829): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (15:33:25.956): No touch devices found DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (15:33:28.362): Loaded synthDriver oneCore DEBUGWARNING - core.main (15:33:28.362): Slow starting core (6.32 sec) DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (15:33:28.362): No CLDR data for locale en_US INFO - core.main (15:33:28.980): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (15:33:28.980): Braille input initialized INFO - braille.initialize (15:33:28.980): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (15:33:28.996): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:33:29.346): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (15:33:29.818): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (15:33:29.947): No touch devices found DEBUGWARNING - Python warning (15:33:34.384): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (15:33:34.607): NVDA initialized DEBUGWARNING - watchdog._watcher (15:34:17.881): Trying to recover from freeze, core stack: File "nvda.pyw", line 231, in <module> File "core.pyo", line 519, in main File "wx\core.pyo", line 2134, in MainLoop File "gui\__init__.pyo", line 1003, in Notify File "core.pyo", line 490, in run File "queueHandler.pyo", line 86, in pumpAll File "queueHandler.pyo", line 53, in flushQueue File "eventHandler.pyo", line 62, in _queueEventCallback File "eventHandler.pyo", line 150, in executeEvent File "eventHandler.pyo", line 163, in doPreGainFocus File "api.pyo", line 107, in setFocusObject File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\__init__.pyo", line 501, in _get_container File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\IAccessible\__init__.pyo", line 962, in _get_parent File "NVDAObjects\__init__.pyo", line 78, in __call__ File "NVDAObjects\IAccessible\__init__.pyo", line 649, in __init__ File "comtypes\__init__.pyo", line 1160, in QueryInterface
ERROR - RPC process 3228 (nvda_slave.exe) (15:34:20.319): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 93, in main File "comHelper.pyo", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyo", line 180, in GetActiveObject File "comtypes\__init__.pyo", line 1247, in GetActiveObject File "_ctypes/callproc.c", line 946, in GetResult WindowsError: [Error -2147221021] Operation unavailable DEBUGWARNING - Python warning (15:34:20.404): C:\Program Files (x86)\NVDA\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:34:21.678): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) DEBUGWARNING - Python warning (15:35:48.522): C:\Program Files (x86)\NVDA\library.zip\keyboardHandler.py:528: DeprecationWarning: Yield() is deprecated INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:58.546): Developer info for navigator object: name: u'Message' role: ROLE_EDITABLETEXT states: STATE_FOCUSABLE, STATE_MULTILINE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <nvdaBuiltin.appModules.outlook.OutlookWordDocument object at 0x0A624ED0> Python class mro: (<class 'nvdaBuiltin.appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.winword.WordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: RectLTWH(left=7, top=252, width=1569, height=600) value: None appModule: <'outlook' (appName u'outlook', process ID 1536) at address a5e55f0> appModule.productName: u'Microsoft Outlook' appModule.productVersion: u'16.0.12130.20390' TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'> windowHandle: 787432 windowClassName: u'_WwG' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 16 windowThreadID: 3532 windowText: u'Message' displayText: u'' IAccessibleObject: <POINTER(IAccessible) ptr=0x5f6b2a8 at a5d1170> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=787432, objectID=-4, childID=0 IAccessible accName: u'Message' IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, sounds like the installed copy got compatibility mode set. Can you install this portable copy and see if that makes a difference? To do so, run the portable copy, then to go NVDA menu/Tools/Install. Do not check the box for copying portable config to installed version. Say “yes” when User Account Control (UAC) appears, and when “success” message shows up, press Enter to start the installed copy. Then with the installed copy running, open log viewer and send me the beginning part of the log as a reply, as it’ll confirm if indeed this resolved it or NVDA still set to run in compatibility mode. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I created a portable copy and the windows version was 10. Here is the log: INFO - __main__ (13:43:37.826): Starting NVDA INFO - core.main (13:43:38.128): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:43:38.128): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:43:38.529): NVDA version 2019.2.1 INFO - core.main (13:43:38.529): Using Windows version 10.0.18363 workstation INFO - core.main (13:43:38.529): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:43:38.529): Using comtypes version 1.1.7 INFO - core.main (13:43:38.529): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (13:43:38.809): Touch only supported on installed copies DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (13:43:39.575): Loaded synthDriver oneCore INFO - core.main (13:43:39.575): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (13:43:39.579): Braille input initialized INFO - braille.initialize (13:43:39.585): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (13:43:39.595): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:43:39.930): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (13:43:40.165): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (13:43:40.288): Touch only supported on installed copies DEBUGWARNING - Python warning (13:43:44.013): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (13:43:44.352): NVDA initialized DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (13:43:44.553): No CLDR data for locale en_US DEBUGWARNING - Python warning (13:43:45.071): C:\Users\Owner\AppData\Local\Temp\nsc86E4.tmp\app\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:43:56.013): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:44:23.746): Developer info for navigator object: name: u'nvda_2019.2.1.exe' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at 0x055ED030> Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: '' location: RectLTWH(left=460, top=591, width=478, height=22) value: '' appModule: <'explorer' (appName u'explorer', process ID 1828) at address 501e6f0> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.18362.1' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 459738 windowClassName: u'DirectUIHWND' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 0 windowThreadID: 728 windowText: u'' displayText: u'nvda_2019.2.1.exe 11/ 28/ 2019 6:33 PM 23,830 KB' UIAElement: <POINTER(IUIAutomationElement) ptr=0x8d77b88 at 5597c10> UIA automationID: 515 UIA frameworkID: DirectUI UIA runtimeID: (1828, 254995280, 0) UIA providerDescription: [pid:1828,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:explorerframe.dll)] UIA className: UIItem UIA patterns available: LegacyIAccessiblePattern, InvokePattern, ScrollItemPattern, SelectionItemPattern, ValuePattern
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, If so, I’m afraid that this is beyond my area. Let’s try one more step:
Paste the log fragment as a reply to this email so Quentin and I can figure out exactly what is up. If Windows version line says “10.0.18363”, chances are that it is specific to the installed version; if it says “6.2.9200”, chances are that it is unique to your computer. If so, I advise a non-destructive feature update reinstallation – download Media Creation Tool for 1909, create an ISO, open the resulting ISO file, run setup.exe, and tell the installer to upgrade while keeping everything. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I re installed nvda and did your suggestions about the add ons. I still get version 8.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:
If OneCore comes up, restart NVDA with partial add-on functionality. To do so:
If this does not help, reinstall NVDA from scratch. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
When I press nvda shift plus 6 it says windows 8 64 bit. I hope this helps.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, You may need to manually type these lines into Python Console. Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Jacob,
What I did was copy and paste the lines just as Joseph typed them.
Jacob Kruger +2782 413 4791 "Resistance is futile...but, acceptance is versatile..." On 2019-11-28 10:23 AM, Gary Metzler wrote:
|
|
|
|
Re: nvda 2019.3 incompatible addons list
Hi rui.
toggle quoted messageShow quoted text
Its good to know that it works. This does make me wander though on how updated the addons site is and if its kept updated regularly with compatible versions. In some ways if the links are the ame or something can be done with github, it should be automated I realise its manual and I did bring this up before, I realise it can't be kept updated all the time whenthings are released, still I do check the site and updater for addons from time to time and if things are more updated than either of those databases there may be an issue at some point in time.
On 2/12/2019 3:21 am, Rui Fontes wrote:
Hello Shaun!
|
|
|
|
Re: NVDA not reading MS-Word Dialog Boxes
Aman Agrawal <amanagrawal456@...>
Yes all are same
On Sun, 1 Dec, 2019, 21:21 Antony Stone, <antony.stone@...> wrote: Are all the laptops identical, running the same version of Windows, and the
|
|
|
|
Re: NVDA not reading MS-Word Dialog Boxes
Antony Stone
Are all the laptops identical, running the same version of Windows, and the
toggle quoted messageShow quoted text
same version of Word? If not, please tell us about the differences. Antony.
On Sunday 01 December 2019 at 12:54:34, Aman Agrawal wrote:
I have installed NVDA in 5 laptops. But in 3 laptops I'm facing a problem --
"A person lives in the UK, but commutes to France daily for work. He belongs in the UK." - From UK Revenue & Customs notice 741, page 13, paragraph 3.5.1 - http://tinyurl.com/o7gnm4 Please reply to the list; please *don't* CC me.
|
|
|
|
NVDA not reading MS-Word Dialog Boxes
Aman Agrawal <amanagrawal456@...>
I have installed NVDA in 5 laptops. But in 3 laptops I'm facing a problem which i think you can solve.
In MS Word, while opening any dialog box ( like of Font ) , the NVDA is not reading the contents/ options provided in the dialog box.
Please help me out to solve this problem so that it can be a great help for some special Students.
Waiting for an early reply.
Thanks & Regards
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Hi, Glad it is resolved for you. Let us know if you run into other issues in the future. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Sunday, December 1, 2019 3:30 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi Joseph,
I did a reset of my windows and now I get the right version number. Thanks for all your help.
Sent from Mail for Windows 10
From: Joseph Lee
Hi, Try going to addons.nvda-project.org. I think this issue is way beyond add-ons – it is NVDA compatibility mode problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
For some reason I can’t get to the nvda add on page. I want to show the ms tech the problem I am having How can I get to the add on page? Thanks for any help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Complete reset as in performing a Windows 10 reset with no user data left. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Hi, At this point, I’m out of options except for a complete reset. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a repair last night but,it didn’t help. Thanks for all your help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, this confirms the suspicion that somehow NVDA is told to run in compatibility mode when installed. If removing and reinstalling NVDA from scratch (including via portable copy) doesn’t work, chances are that this might be a registry issue that is way beyond our control. The most effective way to resolve this (apart from changing compatibility mode settings, which might be something not many people are familiar with) is a non-destructive Windows 10 reinstall using Media Creation Tool for Version 1909. Failing that, a reset might be in order (you must reinstall desktop apps including NVDA if you decide to go down this path). Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I ran the portable copy and installed from there but, I still get version 8 .
Here is the log:
INFO - __main__ (15:33:23.819): Starting NVDA INFO - core.main (15:33:24.457): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:33:24.457): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:33:24.829): NVDA version 2019.2.1 INFO - core.main (15:33:24.829): Using Windows version 6.2.9200 workstation INFO - core.main (15:33:24.829): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:33:24.829): Using comtypes version 1.1.7 INFO - core.main (15:33:24.829): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (15:33:25.956): No touch devices found DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (15:33:28.362): Loaded synthDriver oneCore DEBUGWARNING - core.main (15:33:28.362): Slow starting core (6.32 sec) DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (15:33:28.362): No CLDR data for locale en_US INFO - core.main (15:33:28.980): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (15:33:28.980): Braille input initialized INFO - braille.initialize (15:33:28.980): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (15:33:28.996): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:33:29.346): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (15:33:29.818): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (15:33:29.947): No touch devices found DEBUGWARNING - Python warning (15:33:34.384): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (15:33:34.607): NVDA initialized DEBUGWARNING - watchdog._watcher (15:34:17.881): Trying to recover from freeze, core stack: File "nvda.pyw", line 231, in <module> File "core.pyo", line 519, in main File "wx\core.pyo", line 2134, in MainLoop File "gui\__init__.pyo", line 1003, in Notify File "core.pyo", line 490, in run File "queueHandler.pyo", line 86, in pumpAll File "queueHandler.pyo", line 53, in flushQueue File "eventHandler.pyo", line 62, in _queueEventCallback File "eventHandler.pyo", line 150, in executeEvent File "eventHandler.pyo", line 163, in doPreGainFocus File "api.pyo", line 107, in setFocusObject File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\__init__.pyo", line 501, in _get_container File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\IAccessible\__init__.pyo", line 962, in _get_parent File "NVDAObjects\__init__.pyo", line 78, in __call__ File "NVDAObjects\IAccessible\__init__.pyo", line 649, in __init__ File "comtypes\__init__.pyo", line 1160, in QueryInterface
ERROR - RPC process 3228 (nvda_slave.exe) (15:34:20.319): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 93, in main File "comHelper.pyo", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyo", line 180, in GetActiveObject File "comtypes\__init__.pyo", line 1247, in GetActiveObject File "_ctypes/callproc.c", line 946, in GetResult WindowsError: [Error -2147221021] Operation unavailable DEBUGWARNING - Python warning (15:34:20.404): C:\Program Files (x86)\NVDA\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:34:21.678): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) DEBUGWARNING - Python warning (15:35:48.522): C:\Program Files (x86)\NVDA\library.zip\keyboardHandler.py:528: DeprecationWarning: Yield() is deprecated INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:58.546): Developer info for navigator object: name: u'Message' role: ROLE_EDITABLETEXT states: STATE_FOCUSABLE, STATE_MULTILINE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <nvdaBuiltin.appModules.outlook.OutlookWordDocument object at 0x0A624ED0> Python class mro: (<class 'nvdaBuiltin.appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.winword.WordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: RectLTWH(left=7, top=252, width=1569, height=600) value: None appModule: <'outlook' (appName u'outlook', process ID 1536) at address a5e55f0> appModule.productName: u'Microsoft Outlook' appModule.productVersion: u'16.0.12130.20390' TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'> windowHandle: 787432 windowClassName: u'_WwG' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 16 windowThreadID: 3532 windowText: u'Message' displayText: u'' IAccessibleObject: <POINTER(IAccessible) ptr=0x5f6b2a8 at a5d1170> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=787432, objectID=-4, childID=0 IAccessible accName: u'Message' IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, sounds like the installed copy got compatibility mode set. Can you install this portable copy and see if that makes a difference? To do so, run the portable copy, then to go NVDA menu/Tools/Install. Do not check the box for copying portable config to installed version. Say “yes” when User Account Control (UAC) appears, and when “success” message shows up, press Enter to start the installed copy. Then with the installed copy running, open log viewer and send me the beginning part of the log as a reply, as it’ll confirm if indeed this resolved it or NVDA still set to run in compatibility mode. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I created a portable copy and the windows version was 10. Here is the log: INFO - __main__ (13:43:37.826): Starting NVDA INFO - core.main (13:43:38.128): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:43:38.128): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:43:38.529): NVDA version 2019.2.1 INFO - core.main (13:43:38.529): Using Windows version 10.0.18363 workstation INFO - core.main (13:43:38.529): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:43:38.529): Using comtypes version 1.1.7 INFO - core.main (13:43:38.529): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (13:43:38.809): Touch only supported on installed copies DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (13:43:39.575): Loaded synthDriver oneCore INFO - core.main (13:43:39.575): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (13:43:39.579): Braille input initialized INFO - braille.initialize (13:43:39.585): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (13:43:39.595): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:43:39.930): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (13:43:40.165): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (13:43:40.288): Touch only supported on installed copies DEBUGWARNING - Python warning (13:43:44.013): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (13:43:44.352): NVDA initialized DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (13:43:44.553): No CLDR data for locale en_US DEBUGWARNING - Python warning (13:43:45.071): C:\Users\Owner\AppData\Local\Temp\nsc86E4.tmp\app\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:43:56.013): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:44:23.746): Developer info for navigator object: name: u'nvda_2019.2.1.exe' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at 0x055ED030> Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: '' location: RectLTWH(left=460, top=591, width=478, height=22) value: '' appModule: <'explorer' (appName u'explorer', process ID 1828) at address 501e6f0> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.18362.1' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 459738 windowClassName: u'DirectUIHWND' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 0 windowThreadID: 728 windowText: u'' displayText: u'nvda_2019.2.1.exe 11/ 28/ 2019 6:33 PM 23,830 KB' UIAElement: <POINTER(IUIAutomationElement) ptr=0x8d77b88 at 5597c10> UIA automationID: 515 UIA frameworkID: DirectUI UIA runtimeID: (1828, 254995280, 0) UIA providerDescription: [pid:1828,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:explorerframe.dll)] UIA className: UIItem UIA patterns available: LegacyIAccessiblePattern, InvokePattern, ScrollItemPattern, SelectionItemPattern, ValuePattern
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, If so, I’m afraid that this is beyond my area. Let’s try one more step:
Paste the log fragment as a reply to this email so Quentin and I can figure out exactly what is up. If Windows version line says “10.0.18363”, chances are that it is specific to the installed version; if it says “6.2.9200”, chances are that it is unique to your computer. If so, I advise a non-destructive feature update reinstallation – download Media Creation Tool for 1909, create an ISO, open the resulting ISO file, run setup.exe, and tell the installer to upgrade while keeping everything. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I re installed nvda and did your suggestions about the add ons. I still get version 8.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:
If OneCore comes up, restart NVDA with partial add-on functionality. To do so:
If this does not help, reinstall NVDA from scratch. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
When I press nvda shift plus 6 it says windows 8 64 bit. I hope this helps.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, You may need to manually type these lines into Python Console. Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Jacob,
What I did was copy and paste the lines just as Joseph typed them.
Jacob Kruger +2782 413 4791 "Resistance is futile...but, acceptance is versatile..." On 2019-11-28 10:23 AM, Gary Metzler wrote:
|
|
|
|
accessing embedded video links in Power point slides
Payal Kapoor
hi,
i am working with a PPT with several slides which have not only graphics as part of the content of a slide, but also links to videos. however, i am unable to access the links(which don't show up as a link there) . i have tried everything but have had no success. when checking using insert+F1, the message very clearly said there were hyperlinks as part of the content. to test that theory, i did copy the content of the slide to a word doc and it shows a link as well. i am using the latest version of NVDA and have tried it with one of the earlier versions of JAWS 18 installed on my Windows 10 laptop. the office version is 2016. the message when focusing on the video in the slide is: video obscured. also, i saw a message about access to the links being blocked. now i don't know which key combination brought that one on. after all that mishmash of information, i would be eternally grateful to anyone who can help me get to the video links. it is critical, since those are part of the training content for work i do. thanks for any possible help. Best,
|
|
|
|
Re: nvda 2019.3 incompatible addons list
Rui Fontes
Hello Shaun!
toggle quoted messageShow quoted text
Regarding add-ons help add-on: 1 - It is not from Doug Lee, but from me with lots of help from community members; 2 - It is already 2019.3 compatible; 3 - You can get the compatible version at: https://www.tiflotecnia.net/addonsHelp.nvda-addon Best regards, Rui Fontes Tiflotecnia, Lda. NVDA portuguese team Às 06:50 de 01/12/2019, Shaun Everiss escreveu:
Thats why I did note enhanced touch gestures has been updated.
|
|
|
|
Monthly Group Rules Reminder for the NVDA Group (nvda@nvda.groups.io)
nvda@nvda.groups.io Group Moderators <nvda@...>
NVDA Group Description: NonVisual Desktop Access (NVDA) is screen reader software. The central purpose of this group is discussing how to use NVDA, either configuring NVDA's settings or familiarizing oneself with its modes and commands. Discussions about which programs are accessible using NVDA, NVDA add-ons, NVDA tutorials and documentation, and configuring synthesizers or Braille displays for use with NVDA are also permitted. It is presumed that the majority of members will be using NVDA, and possibly other screen readers, as part of their daily routine. This being the case, before you post a message you have to consider whether the question you are about to ask is actually about NVDA itself, or about the program you’re using it to access. Questions of the form, How do I use . . . with NVDA?, are very seldom about NVDA, but are almost always about the program being accessed with NVDA. The NVDA Group has a Chat Subgroup (see: https://nvda.groups.io/g/chat, Group Email Addresses section) that has as its purpose the asking of virtually any “off-topic” question about anything you can think of, including just socializing. It should be used for exactly that purpose. The Chat Subgroup has generally had technically focused topics related to using features of the programs that one is using NVDA to access or about other programs that have proven helpful. Only those who are already members of the NVDA Group can subscribe to the Chat Subgroup. Before choosing where to post, please ask yourself the question, “Is what I’m about to ask or offer directly related to controlling or using NVDA, or whether a specific program is accessible with NVDA?” If that can be answered, “Yes,” then post to the NVDA Group, and if the answer is, “No,” then the topic belongs in the NVDA Chat Subgroup. In order to make your experience, and those of all other members, as pleasant as they can be, please follow these practices: 1. Use threaded or conversation view in your e-mail client program or webmail and reading through the entirety of a topic before replying. It gets you completely up to speed and avoids a lot of repetition. If you choose not to use threaded/conversation view, please take the time to read through all messages from the group that are in your inbox prior to adding any reply to the group. It’s the only way you can be sure you’re up to speed on any topic when not using threaded/conversation view. 2. Reading through all new topics before replying, as topics have a tendency to get split upon occasion and often an answer ends up being in a separate topic. 3. If you have reason to believe your question has likely been asked and answered in the past please search the Group Archive first before asking it again. Step-by-Step instructions for searching the group archive using the Groups.io search or a web search engine of your choosing: Searching_the_NVDA_Group_Archive.docx. Please consider using a web search first for questions that have almost certainly been asked frequently and for which myriad answers, often in the form of tutorials, already exist. 4. Think very carefully about the title you are going to give any topic you post. The topic is the first (and, sometimes, only) thing a member sees and that may be how they decide if they’re going to look further. Generic titles, such as “Help Me!,” are not helpful because they give no idea about what. Compare that to something like, “NVDA not reading Excel cell contents,” or, “NVDA setting for pronouncing numbers,” where the exact issue where help is needed is front and center. Even something like, “Need help with the following . . .,” lets the reader know that you are going to present a list of issues. 5. Please avoid, “What is the best . . .?,” topics, because what qualifies as “best” is entirely subjective. Topics of this sort are also always chat topics. If you know you have specific needs then asking, “What {insert program type here} has the following features . . .,” is much more descriptive. If you want to know what programs people like for a specific task, asking, “What’s your favorite . . . and why?,” is far more likely to get you the details you want to have. Notice that none of the above questions ask about whether a program is accessible with NVDA. If you’re asking something like, “Which {insert program class here} is accessible with NVDA?,” then it’s a main group topic. 6. Any topic that is not about using NVDA to accomplish a task, or how to control NVDA, belongs in the chat subgroup, not the main group. All questions about how to use the specific features of a program that you’re using NVDA to access, but not about NVDA itself, belong in the chat subgroup.
Respectful, even if slightly heated, disagreements will occur occasionally and will be tolerated provided what is described next does not occur. Flaming, name calling, instigating arguments for their own sake that do nothing to advance anyone’s knowledge, pointed rudeness, and similar boorish behavior will not be tolerated. If at any point one of you happens upon a message anywhere in the NVDA Group sphere, main or chat, that fits the preceding description then please report it to the group owner either via e-mail at, nvda+owner@nvda.groups.io, or, if you read via the web interface at https://nvda.groups.io/g/nvda/topics, then use the Report this message option that’s a part of the More button at the end of each message. Please don’t add a protest message the topic. If we receive a report and agree with it, the issue will be taken care of promptly.
If you find the amount of traffic from this Group, or any Groups.io group, overwhelming, then please download and read: Controlling the Messages You Receive via E-Mail from Groups.io (docx) Controlling the Messages You Receive via E-Mail from Groups.io (PDF) Each of you has the ability to mute topics that don’t interest you, get digests instead of individual messages, or to set up topic preview for yourself via the Following Only and First Messages Also features used in conjunction with each other. It is up to you to use those to manage your e-mail as you see fit. It’s almost certain that there will be plenty of topics on the chat subgroup that will not be of the least interest to you as an individual. Setting up topic preview lets you pick and choose what you want to continue to see, and this function can be used on any Groups.io group.
Sincerely, Nimer Jaber Brian Vogel
NVDA Group Owner NVDA Group Moderator
To learn more about the NVDA Group, please visit https://nvda.groups.io/g/nvda To start sending messages to members of this group, send email to nvda@nvda.groups.io If you do not wish to belong to the NVDA Group, you may unsubscribe by sending an email to nvda+unsubscribe@nvda.groups.io To see and modify all of your groups, go to https://groups.io
|
|
|
|
Re: Typhoon
molly the blind tech lover
I will be praying for you. God bless you and your family.
toggle quoted messageShow quoted text
-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Jaffar Sidek Sent: Sunday, December 1, 2019 8:11 AM To: nvda@nvda.groups.io Subject: [nvda] Typhoon Hi all. This is strictly Off topic I know, but please keep my family in the philippines in mind as Typhoon Kamuri with winds of up to 150 MPH, bringing with it rain of up to 16 inches is as of now raging across Luzon Island in the Philippines. The hurricane winds is slowly rising, blowing across the area where we live. and is expected to peak early this morning, philippines time. I am expected to return to my family for christmes as I am currently working in Singapore. I only hope that I can return to my wife and kids with the knowledge that they are safe and sound. To those of you who believe in God, please pray for us. If you don't, keep us in your hopes. Thank you.
|
|
|
|
Typhoon
Jaffar Sidek
Hi all. This is strictly Off topic I know, but please keep my family in the philippines in mind as Typhoon Kamuri with winds of up to 150 MPH, bringing with it rain of up to 16 inches is as of now raging across Luzon Island in the Philippines. The hurricane winds is slowly rising, blowing across the area where we live. and is expected to peak early this morning, philippines time. I am expected to return to my family for christmes as I am currently working in Singapore. I only hope that I can return to my wife and kids with the knowledge that they are safe and sound. To those of you who believe in God, please pray for us. If you don't, keep us in your hopes. Thank you.
|
|
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Gary Metzler
Hi Joseph,
I did a reset of my windows and now I get the right version number. Thanks for all your help.
Sent from Mail for Windows 10
From: Joseph Lee
Sent: Friday, November 29, 2019 6:04 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi, Try going to addons.nvda-project.org. I think this issue is way beyond add-ons – it is NVDA compatibility mode problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
For some reason I can’t get to the nvda add on page. I want to show the ms tech the problem I am having How can I get to the add on page? Thanks for any help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Complete reset as in performing a Windows 10 reset with no user data left. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Hi, At this point, I’m out of options except for a complete reset. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a repair last night but,it didn’t help. Thanks for all your help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, this confirms the suspicion that somehow NVDA is told to run in compatibility mode when installed. If removing and reinstalling NVDA from scratch (including via portable copy) doesn’t work, chances are that this might be a registry issue that is way beyond our control. The most effective way to resolve this (apart from changing compatibility mode settings, which might be something not many people are familiar with) is a non-destructive Windows 10 reinstall using Media Creation Tool for Version 1909. Failing that, a reset might be in order (you must reinstall desktop apps including NVDA if you decide to go down this path). Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I ran the portable copy and installed from there but, I still get version 8 .
Here is the log:
INFO - __main__ (15:33:23.819): Starting NVDA INFO - core.main (15:33:24.457): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:33:24.457): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:33:24.829): NVDA version 2019.2.1 INFO - core.main (15:33:24.829): Using Windows version 6.2.9200 workstation INFO - core.main (15:33:24.829): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:33:24.829): Using comtypes version 1.1.7 INFO - core.main (15:33:24.829): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (15:33:25.956): No touch devices found DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (15:33:28.362): Loaded synthDriver oneCore DEBUGWARNING - core.main (15:33:28.362): Slow starting core (6.32 sec) DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (15:33:28.362): No CLDR data for locale en_US INFO - core.main (15:33:28.980): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (15:33:28.980): Braille input initialized INFO - braille.initialize (15:33:28.980): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (15:33:28.996): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:33:29.346): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (15:33:29.818): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (15:33:29.947): No touch devices found DEBUGWARNING - Python warning (15:33:34.384): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (15:33:34.607): NVDA initialized DEBUGWARNING - watchdog._watcher (15:34:17.881): Trying to recover from freeze, core stack: File "nvda.pyw", line 231, in <module> File "core.pyo", line 519, in main File "wx\core.pyo", line 2134, in MainLoop File "gui\__init__.pyo", line 1003, in Notify File "core.pyo", line 490, in run File "queueHandler.pyo", line 86, in pumpAll File "queueHandler.pyo", line 53, in flushQueue File "eventHandler.pyo", line 62, in _queueEventCallback File "eventHandler.pyo", line 150, in executeEvent File "eventHandler.pyo", line 163, in doPreGainFocus File "api.pyo", line 107, in setFocusObject File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\__init__.pyo", line 501, in _get_container File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\IAccessible\__init__.pyo", line 962, in _get_parent File "NVDAObjects\__init__.pyo", line 78, in __call__ File "NVDAObjects\IAccessible\__init__.pyo", line 649, in __init__ File "comtypes\__init__.pyo", line 1160, in QueryInterface
ERROR - RPC process 3228 (nvda_slave.exe) (15:34:20.319): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 93, in main File "comHelper.pyo", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyo", line 180, in GetActiveObject File "comtypes\__init__.pyo", line 1247, in GetActiveObject File "_ctypes/callproc.c", line 946, in GetResult WindowsError: [Error -2147221021] Operation unavailable DEBUGWARNING - Python warning (15:34:20.404): C:\Program Files (x86)\NVDA\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:34:21.678): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) DEBUGWARNING - Python warning (15:35:48.522): C:\Program Files (x86)\NVDA\library.zip\keyboardHandler.py:528: DeprecationWarning: Yield() is deprecated INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:58.546): Developer info for navigator object: name: u'Message' role: ROLE_EDITABLETEXT states: STATE_FOCUSABLE, STATE_MULTILINE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <nvdaBuiltin.appModules.outlook.OutlookWordDocument object at 0x0A624ED0> Python class mro: (<class 'nvdaBuiltin.appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.winword.WordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: RectLTWH(left=7, top=252, width=1569, height=600) value: None appModule: <'outlook' (appName u'outlook', process ID 1536) at address a5e55f0> appModule.productName: u'Microsoft Outlook' appModule.productVersion: u'16.0.12130.20390' TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'> windowHandle: 787432 windowClassName: u'_WwG' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 16 windowThreadID: 3532 windowText: u'Message' displayText: u'' IAccessibleObject: <POINTER(IAccessible) ptr=0x5f6b2a8 at a5d1170> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=787432, objectID=-4, childID=0 IAccessible accName: u'Message' IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, sounds like the installed copy got compatibility mode set. Can you install this portable copy and see if that makes a difference? To do so, run the portable copy, then to go NVDA menu/Tools/Install. Do not check the box for copying portable config to installed version. Say “yes” when User Account Control (UAC) appears, and when “success” message shows up, press Enter to start the installed copy. Then with the installed copy running, open log viewer and send me the beginning part of the log as a reply, as it’ll confirm if indeed this resolved it or NVDA still set to run in compatibility mode. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I created a portable copy and the windows version was 10. Here is the log: INFO - __main__ (13:43:37.826): Starting NVDA INFO - core.main (13:43:38.128): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:43:38.128): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:43:38.529): NVDA version 2019.2.1 INFO - core.main (13:43:38.529): Using Windows version 10.0.18363 workstation INFO - core.main (13:43:38.529): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:43:38.529): Using comtypes version 1.1.7 INFO - core.main (13:43:38.529): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (13:43:38.809): Touch only supported on installed copies DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (13:43:39.575): Loaded synthDriver oneCore INFO - core.main (13:43:39.575): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (13:43:39.579): Braille input initialized INFO - braille.initialize (13:43:39.585): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (13:43:39.595): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:43:39.930): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (13:43:40.165): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (13:43:40.288): Touch only supported on installed copies DEBUGWARNING - Python warning (13:43:44.013): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (13:43:44.352): NVDA initialized DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (13:43:44.553): No CLDR data for locale en_US DEBUGWARNING - Python warning (13:43:45.071): C:\Users\Owner\AppData\Local\Temp\nsc86E4.tmp\app\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:43:56.013): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:44:23.746): Developer info for navigator object: name: u'nvda_2019.2.1.exe' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at 0x055ED030> Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: '' location: RectLTWH(left=460, top=591, width=478, height=22) value: '' appModule: <'explorer' (appName u'explorer', process ID 1828) at address 501e6f0> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.18362.1' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 459738 windowClassName: u'DirectUIHWND' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 0 windowThreadID: 728 windowText: u'' displayText: u'nvda_2019.2.1.exe 11/ 28/ 2019 6:33 PM 23,830 KB' UIAElement: <POINTER(IUIAutomationElement) ptr=0x8d77b88 at 5597c10> UIA automationID: 515 UIA frameworkID: DirectUI UIA runtimeID: (1828, 254995280, 0) UIA providerDescription: [pid:1828,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:explorerframe.dll)] UIA className: UIItem UIA patterns available: LegacyIAccessiblePattern, InvokePattern, ScrollItemPattern, SelectionItemPattern, ValuePattern
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, If so, I’m afraid that this is beyond my area. Let’s try one more step:
Paste the log fragment as a reply to this email so Quentin and I can figure out exactly what is up. If Windows version line says “10.0.18363”, chances are that it is specific to the installed version; if it says “6.2.9200”, chances are that it is unique to your computer. If so, I advise a non-destructive feature update reinstallation – download Media Creation Tool for 1909, create an ISO, open the resulting ISO file, run setup.exe, and tell the installer to upgrade while keeping everything. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I re installed nvda and did your suggestions about the add ons. I still get version 8.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:
If OneCore comes up, restart NVDA with partial add-on functionality. To do so:
If this does not help, reinstall NVDA from scratch. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
When I press nvda shift plus 6 it says windows 8 64 bit. I hope this helps.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, You may need to manually type these lines into Python Console. Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Jacob,
What I did was copy and paste the lines just as Joseph typed them.
Jacob Kruger +2782 413 4791 "Resistance is futile...but, acceptance is versatile..." On 2019-11-28 10:23 AM, Gary Metzler wrote:
|
|
|
|
Re: Why does NVDA say selected instead at times?
Gene
I'm curious what changed in NVDA. It didn't
used to do that. I don't know when it started.
Gene
----- Original Message -----
From: Laughing Thunder
Sent: Saturday, November 30, 2019 10:56 PM
Subject: Re: [nvda] Why does NVDA say selected instead at
times? On Nov 30, 2019, at 4:38 PM, Gene <gsasner@...> wrote:
-- Laughingthunder
|
|
|
|
Programming Braille Displays
Pele West
Hi Everyone
I am quite new to NVDA and have not played with it very much. Is there a way, either in NVDA itself or with an addon, to program the keys on braille displays as one can in JAWS? I have a Brailliant 64 and my husband has an Alva 680 and we both use the keys to perform lot of actions. Thanks pele West
|
|
|
