Date   
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
Sent: Friday, November 29, 2019 2:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 4:25 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 1:24 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 1:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 4:11 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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).
Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Friday, November 29, 2019 12:38 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 1:57 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Friday, November 29, 2019 10:51 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Thursday, November 28, 2019 7:58 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

If so, I’m afraid that this is beyond my area. Let’s try one more step:

  1. Download NVDA 2019.2.1.
  2. Do not install – rather, create a portable copy somewhere you can remember.
  3. Start the portable copy.
  4. With the portable copy started, press NVDA+F1 to open log viewer.
  5. Copy and paste the log up to and including the words “NVDA initialized”.

 

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
Sent: Thursday, November 28, 2019 4:49 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Thursday, November 28, 2019 12:20 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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:

  1. Restart with all add-ons disabled.
  2. Listen carefully to which synthesizer is now in use; if it is Espeak, then you will need to reinstall NVDA from scratch; if it is Windows OneCore, chances are that there might be an add-on other than Windows 10 App Essentials and Add-on Updater that messed up NVDA’s manifest information.

 

If OneCore comes up, restart NVDA with partial add-on functionality. To do so:

  1. Open Add-ons Manager (NVDA menu/Tools/Manage add-ons).
  2. Disable one add-on at a time and restart NVDA after disabling each one. Do not disable Resource Monitor as we need it to check Windows version.
  3. After disabling an add-on and restarting NVDA, press NVDA+Shift+Number row 6 to verify that you are using Windows 10.
  4. As soon as you find that NVDA says Windows 10, thee the just disabled add-on might be to blame.
  5. To verify step 4, enable all add-ons except the offending one and see if NVDA now reports itself as running on Windows 10.

 

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
Sent: Thursday, November 28, 2019 8:58 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Thursday, November 28, 2019 9:49 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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
Sent: Thursday, November 28, 2019 6:27 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

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:

Hi Joseph,

 

After I enter each line I get the error win version not defined.

I hope this helps.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 7:03 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Hmmm, you get “False” when you’ve got 1909… Let’s try this method:

 

  1. Go back to Python Console (Control+NVDA+Z).
  2. Type the following as exactly as shown (press Enter after each line and listen carefully to what NVDA says):

 

import winVersion

winVersion.winVersion

winVersion.isWin10()

winVersion.isWin10(version=1607)

winVersion.isWin10(version=1709)

winVersion.isWin10(version=1803)

winVersion.isWin10(version=1809)

 

NVDA will first announce Windows version information (major, minor, build, platform, service pack), then for each Windows 10 release we have, “True” or “False”.

Cheers,

Joseph

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I did what you suggested and I get a false response.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:32 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

That’s strange. Let’s try:

  1. Open Python Console (Control+NVDA+Z).
  2. Type the following as exactly as I tell you:

 

import winVersion

winVersion.isWin10(version=1809)

 

Press Enter after each line. If it says “True”, then there should not be a reason for Windows 10 App Essentials to complain that you’ve got an older Windows release.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I got the add on manually but, when I went to install it it said I was using an older version of windows.

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 6:14 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

Actually, it is compatible with 1809 and later. I’m beginning to wonder if this affects anyone using Add-on Updater, and if this is the case, it isn’t Windows 10 App Essentials at all.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Wednesday, November 27, 2019 3:09 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi,

I think I know why – I’ll go ahead and release another version in a few moments. Sorry about that.

Cheers,

Joseph

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Sent: Wednesday, November 27, 2019 3:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi Joseph,

 

I’m sorry to say I am getting the error not compatible with this version of windows.  I am using windows 10 1909 and the latest nvda.  

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Wednesday, November 27, 2019 2:38 PM
To: nvda-addons@nvda-addons.groups.io
Subject: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease

 

Hi all,

 

In a few moments Windows 10 App Essentials 19.11.3 will be made available. This release is a localization and documentation update.

 

A few important notes:

 

  • Windows 10 20H1 is now formally known as Version 2004. Although Windows 10 App Essentials does support Version 2004, formal support won’t begin until early next year.
  • A version scheduled for early next year will retire support for EdgeHTML-based Microsoft Edge from this add-on.

 

Cheers,

Joseph

 

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 -----
Sent: Saturday, November 30, 2019 10:56 PM
Subject: Re: [nvda] Why does NVDA say selected instead at times?

This happens because text in the run dialogue is selected by default when the dialogue opens. When you use the up and down arrow keys to move through the history of commands you have entered, the text changes, but the selection remains. Windows simply puts the new text into the text field every time you press up or down, but the text never gets unselected before being changed.


On Nov 30, 2019, at 4:38 PM, Gene <gsasner@...> wrote:


I updated to Windows 7 Service pack 1 recently to try to solve a problem which wasn’t solved in that way.  I had put it off because there was a version of a program I can’t run after the update.  It’s a little less convenient but I can run a newer version and I almost never run it anyway. 
 
Which is to explain why I hadn’t played with newer versions of NVDA for a good while.  But now, I’m curious about something.  When I am in the run dialog and up and down arrow in the list of things I have run, NVDA says the word instead off and on.  It might say Notepad selected, then if I down arrow, it might say c:\audio selected instead or maybe Wordpad selected instead.  This isn’t consistent and it doesn’t do this in Windows Explorer.  I’m curious why that is.
 
Gene

--
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

Re: nvda 2019.3 incompatible addons list

 

Well to be honest, if your noncompatible addon appears on the list and you know it is thats fine.

Its more for those that don't know, don't care or just havn't looked in a while.

I don't use all addons but I thought I should really put a buck in and see what worked or not.

I usually don't test alphas but since I have been arguing over the last 2 days sooner or later I'd be asked to put my money where my mouth was and decided that I'd better do so, especially since I had some time to do it.

As I said if your addon is on the list or will be on the list and that goes to all developers that know thats fine.

It would be nice to have more devs tell us if they are or not.

On 1/12/2019 7:59 pm, Joseph Lee wrote:
Hi,
Don't worry - my issue was use of outdated add-ons and claiming they are incompatible when in fact compatible versions exist. The good news is that more add-ons people are realizing that, before too long, they will feel the urgency to change, and for some, they'll realize this when it is too late. I myself am keeping a very close eye on it, and so is Quentin.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Again, joseph, I was not targeting you personally, you're not the problem,

You as community leader were first out of the gun its everyone else.

Well those that havn't checked in at any rate.

Of those, I assume a lot of them unless they have been under a rock know about this.

What may happen is we may have to see what happens on release and how many addons don't pop out.

I think inside the community we are pritty square with a lot of addons.

I repeat, you are not the problem, there may be a few that are either lerking or outside the list that don't keep up with events maybe they have missed stuff.

Everyone on the list that hasn't responded so far will be probably be working on things.

I do know not everyone speaks here.



On 1/12/2019 7:39 pm, Joseph Lee wrote:
HI,
Actually, ObjPad is compatible, too - since a few months ago. I guarantee that all my add-ons (except Screen Curtain) are NVDA 2019.3 ready - some are already gearing for future of Python.
Cheers,
Joseph P.S. Apologies for rapid-fire posts.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph
Lee via Groups.Io
Sent: Saturday, November 30, 2019 10:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun
Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.













logging into Zoom With Microsoft Edge Dev and NVDA

 

Hello, everyone. I"m having an issue, as stated in the subject. When I launch Zoom, and have Edge Dev set as default browser, It brings up a dialog/page. I cannot close it. I cannot move away from it using shift+tab. It is some kind of alert thing going on. I have to close it from task manager.


When it is first launched, I can navigate to a button that says "launch Zoom". It spawns another of these pages/dialogs. Nothing happens. Zoom is not logged into anything. I've not tried to log in using Google, or single sign-in. I login to Zoom via Facebook.


My roommate can login just fine. He uses same version of Edge Dev as I do. However, he uses 2019.2.1. I'm using the latest alpha (NVDA alpha-19346,0c0d88aa). He uses same version of Zoom as well. He logs into Zoom via Facebook. Any help with this one is appreciated.


This is a chunk of my log. Maybe it will help, maybe it won't.


Developer info for navigator object:
name: 'Login with Facebook - Zoom - Microsoft Edge Dev'
role: ROLE_PANE
roleText: None
states:
isFocusable: False
hasFocus: False
Python object: <NVDAObjects.IAccessible.ia2Web.Ia2Web object at 0x012C5270>
Python class mro: (<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'>, <class 'object'>)
description: ''
location: RectLTWH(left=40, top=30, width=1554, height=980)
value: ''
appModule: <'appModuleHandler' (appName 'msedge', process ID 6708) at address 1320fd0>
appModule.productName: 'Microsoft Edge'
appModule.productVersion: '80.0.334.4'
TextInfo: <class 'NVDAObjects.IAccessible.IA2TextTextInfo'>
windowHandle: 2688070
windowClassName: 'Chrome_WidgetWin_1'
windowControlID: 0
windowStyle: 382664704
extendedWindowStyle: 256
windowThreadID: 24208
windowText: 'Login with Facebook - Zoom and 1 more page - Personal - Microsoft Edge'
displayText: ''
IAccessibleObject: <POINTER(IAccessible2) ptr=0x5ab750c at 7943120>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=2688070, objectID=-4, childID=0
IAccessible accName: 'Login with Facebook - Zoom - Microsoft Edge Dev'
IAccessible accRole: ROLE_SYSTEM_PANE
IAccessible accState:  (0)
IAccessible accDescription: ''
IAccessible accValue: ''
IAccessible2 windowHandle: 2688070
IAccessible2 uniqueID: -80
IAccessible2 role: ROLE_SYSTEM_PANE
IAccessible2 states: IA2_STATE_OPAQUE (1024)
IAccessible2 attributes: 'class:BrowserRootView;'

Re: nvda 2019.3 incompatible addons list

Mr. Wong Chi Wai, William <cwwong.pro@...>
 

I agree with Joseph.

Posting these kind of info should be careful and otherwise you are just spreading fake info and missleading NVDA users.


Joseph Lee 於 1/12/2019 14:33 寫道:

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.







Re: nvda 2019.3 incompatible addons list

 

Hi,
Don't worry - my issue was use of outdated add-ons and claiming they are incompatible when in fact compatible versions exist. The good news is that more add-ons people are realizing that, before too long, they will feel the urgency to change, and for some, they'll realize this when it is too late. I myself am keeping a very close eye on it, and so is Quentin.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:54 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Again, joseph, I was not targeting you personally, you're not the problem,

You as community leader were first out of the gun its everyone else.

Well those that havn't checked in at any rate.

Of those, I assume a lot of them unless they have been under a rock know about this.

What may happen is we may have to see what happens on release and how many addons don't pop out.

I think inside the community we are pritty square with a lot of addons.

I repeat, you are not the problem, there may be a few that are either lerking or outside the list that don't keep up with events maybe they have missed stuff.

Everyone on the list that hasn't responded so far will be probably be working on things.

I do know not everyone speaks here.



On 1/12/2019 7:39 pm, Joseph Lee wrote:
HI,
Actually, ObjPad is compatible, too - since a few months ago. I guarantee that all my add-ons (except Screen Curtain) are NVDA 2019.3 ready - some are already gearing for future of Python.
Cheers,
Joseph P.S. Apologies for rapid-fire posts.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph
Lee via Groups.Io
Sent: Saturday, November 30, 2019 10:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun
Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.











Re: nvda 2019.3 incompatible addons list

 

Again, joseph, I was not targeting you personally, you're not the problem,

You as community leader were first out of the gun its everyone else.

Well those that havn't checked in at any rate.

Of those, I assume a lot of them unless they have been under a rock know about this.

What may happen is we may have to see what happens on release and how many addons don't pop out.

I think inside the community we are pritty square with a lot of addons.

I repeat, you are not the problem, there may be a few that are either lerking or outside the list that don't keep up with events maybe they have missed stuff.

Everyone on the list that hasn't responded so far will be probably be working on things.

I do know not everyone speaks here.

On 1/12/2019 7:39 pm, Joseph Lee wrote:
HI,
Actually, ObjPad is compatible, too - since a few months ago. I guarantee that all my add-ons (except Screen Curtain) are NVDA 2019.3 ready - some are already gearing for future of Python.
Cheers,
Joseph P.S. Apologies for rapid-fire posts.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Saturday, November 30, 2019 10:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.










Re: nvda 2019.3 incompatible addons list

 

Thats why I did note enhanced touch gestures has been updated.

A lot of these are addons I don't use, the only older addons by truth I use are jgt, addons help, image describer, and teamtalk.

I am not sure about addons help but dug lee probably has an updated addon in the list.

I know you would keep your addons up to date, its everything else.

image describer is a new one but I am unsure of its status but I don't use it much.

The interactive fiction addon is quite good for what it is but nothing has been done to it for ages probably because its probably all its going to be.

On 1/12/2019 7:33 pm, Joseph Lee wrote:
Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.








.

Re: nvda 2019.3 incompatible addons list

 

HI,
Actually, ObjPad is compatible, too - since a few months ago. I guarantee that all my add-ons (except Screen Curtain) are NVDA 2019.3 ready - some are already gearing for future of Python.
Cheers,
Joseph P.S. Apologies for rapid-fire posts.

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Sent: Saturday, November 30, 2019 10:34 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda 2019.3 incompatible addons list

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.

Re: nvda 2019.3 incompatible addons list

 

Hi,
I strongly advise running your tests again AFTER updating ALL of these add-ons. I'm happy and disappointed to find that one of my own add-ons is listed in there, especially an outdated version (I don't want to sound rude, but Enhanced Touch Gestures has been compatible since September).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:29 PM
To: nvda@nvda.groups.io
Subject: [nvda] nvda 2019.3 incompatible addons list

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.

nvda 2019.3 incompatible addons list

 

Hi note, this is a list of addons that are not compatible at all at least from the manafests and were tried on a lot of packages.

These are not all addons, some I know have been released, some of these are being worked on and I have allready notified the author of one of them privately.

Excluding the addon I have talked about here is the list.

Note, I think enhanced touch gestures is compatible now.

teamtalk fixes 0.98 found on bareware website.
emoticons 11.0
report symbols 4.8
enhancedTouchGestures-19.05.1
addonsHelp-2.0
ImageDescriber-1.2.1
Mozilla-1.7
dropbox-4.3
objPad-16.12
IfInterpreters-1.1
teamViewer-2.2
Note I have not updated these in a while as I don't use some of them.

I do wander if addons documentation could be included in core help menu.

The if interpriters would be nice to.

Re: latest snapshot of nvda 2019.3 test run

 

Hi,
To really find out if this is specific to add-ons, try running it with add-ons disabled and see if the issue occurs again. If not, chances are that it is an add-on that forgets to remove its settings panel properly (seen it at least once myself while doing add-on code review).
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Shaun Everiss
Sent: Saturday, November 30, 2019 10:18 PM
To: nvda@nvda.groups.io
Subject: [nvda] latest snapshot of nvda 2019.3 test run

I have a few issues with 2019.3 build alpha 2019.3.046.

on exiting after changing language in preffs I get the following log fragment.

INFO - core.main (19:10:19.440) - MainThread (11692):
Exiting
ERROR - gui.terminate (19:10:19.440) - MainThread (11692):
Destroyed but not deleted instance of settings dialog exists:
<gui.settingsDialogs.NVDASettingsDialog object at 0x0A5EBBC0>

I am testing this mainly to see what addons screw up and what don't to see what needs fixing.

latest snapshot of nvda 2019.3 test run

 

I have a few issues with 2019.3  build alpha 2019.3.046.

on exiting after changing language in preffs I get the following log fragment.

INFO - core.main (19:10:19.440) - MainThread (11692):
Exiting
ERROR - gui.terminate (19:10:19.440) - MainThread (11692):
Destroyed but not deleted instance of settings dialog exists: <gui.settingsDialogs.NVDASettingsDialog object at 0x0A5EBBC0>

I am testing this mainly to see what addons screw up and what don't to see what needs fixing.

Re: Why does NVDA say selected instead at times?

Laughing Thunder
 

This happens because text in the run dialogue is selected by default when the dialogue opens. When you use the up and down arrow keys to move through the history of commands you have entered, the text changes, but the selection remains. Windows simply puts the new text into the text field every time you press up or down, but the text never gets unselected before being changed.


On Nov 30, 2019, at 4:38 PM, Gene <gsasner@...> wrote:


I updated to Windows 7 Service pack 1 recently to try to solve a problem which wasn’t solved in that way.  I had put it off because there was a version of a program I can’t run after the update.  It’s a little less convenient but I can run a newer version and I almost never run it anyway. 
 
Which is to explain why I hadn’t played with newer versions of NVDA for a good while.  But now, I’m curious about something.  When I am in the run dialog and up and down arrow in the list of things I have run, NVDA says the word instead off and on.  It might say Notepad selected, then if I down arrow, it might say c:\audio selected instead or maybe Wordpad selected instead.  This isn’t consistent and it doesn’t do this in Windows Explorer.  I’m curious why that is.
 
Gene

--
Laughingthunder

Re: Nvda keeps repeating every thing twice on the whats new page with alpha.

Quentin Christensen
 

As Joseph said, which browser are you using?

Firefox does seem to repeat a couple of things at the start, even moreso than Chrome - partly also, the title of the page "What's new in NVDA" is the same as the first heading level1 which starts the page, so that text gets read at least twice.  After that, the version number, new features etc, should all be read only once.

On Sat, Nov 30, 2019 at 10:18 AM Joseph Lee <joseph.lee22590@...> wrote:
Hi,
Which web browser is this?
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Kevin Cussick via Groups.Io
Sent: Friday, November 29, 2019 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] Nvda keeps repeating every thing twice on the whats new page with alpha.

Hi  Nvda devs,   I have now for at least 3 weeks now when reading the
what's new under the help of Nvda alphahad the problem of Nvda repeating
everything twice,   it did not used to do this!   every thing and every
link it speaks twice it is very annoying. tried espeak and the sinth I
use is RH voice,   any ideas? thanking you all in advance.








--
Quentin Christensen
Training and Support Manager

Re: In-Process 29th November

Quentin Christensen
 

Hi Zahra,

Good question.  Most of the time it comes back to developers not knowing about accessibility, what is required, or how to test for it.  Ideally, developers should be taught how to make accessible software (& web sites) when learning to create in the first place.  Unfortunately it's not included in most courses.  Unless a developer has a personal connection with someone who needs accessible content, they might never consider it.  For that reason, we recommend not usually going in "all guns blazing" and instead explaining the problem and what you need.  If you do that and a large software company comes back and says "We know it's not accessible, and we don't care", then, by all means, let rip at them, sue them, encourage people to boycott them, etc.  If it's something designed by someone on their own in their free time, they may have difficulty rebuilding it - it is definitely easier to make something accessible from the outset than to have to fix it later.

Sometimes, a developer will make something which fits how they work, so if they rely heavily on the mouse, they might not consider keyboard shortcuts.  Or if they add keyboard shortcuts, they might not realise the difficulty that many users have in executing three or four key combinations.

Standards such as WCAG exist to prompt developers to ensure they consider things like contrast, text size and navigation.  In terms of steps to make software accessible - the exact procedure will vary depending on the development environment and language being used etc.  So standards and pointers of things to be aware of like WCAG and like the #NoMouse challenge I mentioned in In-Process are good places to start.

Kind regards

Quentin.

On Sat, Nov 30, 2019 at 5:01 AM zahra <nasrinkhaksar3@...> wrote:
hi quentin.
thanks so much for your great in process.
i wonder, why developers of softwaresdont make programs accessible for
all people?
does accessibility need really furthere steps and a lot of times?
or, the programmers think that there is noone who use keyboard!
i heard even some sighted users, use keyboard instead of mouse.
can you send a link for me which explains the process for making
accessible softwares?
God bless you and His infinite mercy i pray for you!

On 11/29/19, Quentin Christensen <quentin@...> wrote:
> Hi everyone,
>
> Firstly, Happy Thanksgiving to all our American friends!
>
> We've got a big In-Process for you this week:
> https://www.nvaccess.org/post/in-process-29th-november/
>
> It's choc-full of Information about NVDA 2019.3, a wrap-up of NVDACon, the
> #NoMouse challenge, and an in-depth look at how to advocate for software &
> web accessibility!
>
> Enjoy :)
>
> Kind regards
>
> Quentin.
> --
> Quentin Christensen
> Training and Support Manager
>
> Web: www.nvaccess.org
> Training: https://www.nvaccess.org/shop/
> Certification: https://certification.nvaccess.org/
> User group: https://nvda.groups.io/g/nvda
> Facebook: http://www.facebook.com/NVAccess
> Twitter: @NVAccess <https://twitter.com/NVAccess>
>
>
>
>


--
By God,
were I given all the seven heavens
with all they contain
in order that
I may disobey God
by depriving an ant
from the husk of a grain of barley,
I would not do it.
imam ali





--
Quentin Christensen
Training and Support Manager

Why does NVDA say selected instead at times?

Gene
 

I updated to Windows 7 Service pack 1 recently to try to solve a problem which wasn’t solved in that way.  I had put it off because there was a version of a program I can’t run after the update.  It’s a little less convenient but I can run a newer version and I almost never run it anyway. 
 
Which is to explain why I hadn’t played with newer versions of NVDA for a good while.  But now, I’m curious about something.  When I am in the run dialog and up and down arrow in the list of things I have run, NVDA says the word instead off and on.  It might say Notepad selected, then if I down arrow, it might say c:\audio selected instead or maybe Wordpad selected instead.  This isn’t consistent and it doesn’t do this in Windows Explorer.  I’m curious why that is.
 
Gene

Important community add-ons website update: Word add-on declared end of life, removed from add-ons website

 

Dear NVDA community,

 

It is with heavy heart to announce that, due to no active development in the last six years and potential issues with NVDA 2019.2.1 and upcoming 2019.3, Microsoft Word add-on hosted on community add-ons website will be no more, effective immediately. This add-on introduced features such as track changes announcement and other features, features that are now part of NVDA 2019.2.1. Also, this add-on is not compatible with upcoming NVDA 2019.3.

 

If you need features from this add-on (particularly for old NVDA versions), feel free to continue to use this add-on, otherwise the add-ons community advises uninstalling the add-on.

 

Thank you.

Cheers,

Joseph

Re: Weather Plus can't find a city?

molly the blind tech lover
 

Hi.

I really like this add-on ☺ I love the sound effects it makes for different weather conditions, like rain or snow. It’s really cool ☺

 

From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Adriano Barbieri via Groups.Io
Sent: Saturday, November 30, 2019 10:40 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Weather Plus can't find a city?

 

Hi,

There are some options that help in finding a city, ...
Enter:

g:monterrey, mexico
or:
p:monterrey, mexico

or:

t:monterrey, mexico

The search options are explained in the help window, press F1 to show it.

Regarsds
adriano

 

Il 30/11/2019 13:28, Gerardo Corripio ha scritto:

I’m trying to add the city of Monterrey, Mexico (about six and a half hours northwestfrom Tampico where I am), but it doesn’t seem to find it! Where could I go, to locate the code or key, that’ll takkeWeather Gods the city I’mlooking for then? Thanks for any info.

 

                                                                                              Enviado desde Correo para Windows 10