I will be praying for you. God bless you and your family.

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

Hi,

Glad it is resolved for you. Let us know if you run into other issues in the future.

Cheers,

Joseph

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

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

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.

Hi,

Complete reset as in performing a Windows 10 reset with no user data left.

Cheers,

Joseph

Hi,

At this point, I’m out of options except for a complete reset.

Cheers,

Joseph

Hi Joseph,

I did a repair last night but,it didn’t help.  Thanks for all your help.

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

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

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

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

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

Hi Joseph,

I re installed nvda and did your suggestions about the add ons.  I still get version 8.

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

Hi Joseph,

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

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

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

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

Hello Shaun!

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.

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.









.

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.

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

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

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.

Hi,

Complete reset as in performing a Windows 10 reset with no user data left.

Cheers,

Joseph

Hi,

At this point, I’m out of options except for a complete reset.

Cheers,

Joseph

Hi Joseph,

I did a repair last night but,it didn’t help.  Thanks for all your help.

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

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

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

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

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

Hi Joseph,

I re installed nvda and did your suggestions about the add ons.  I still get version 8.

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

Hi Joseph,

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

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

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

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

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.









.

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

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.

Hi,

Complete reset as in performing a Windows 10 reset with no user data left.

Cheers,

Joseph

Hi,

At this point, I’m out of options except for a complete reset.

Cheers,

Joseph

Hi Joseph,

I did a repair last night but,it didn’t help.  Thanks for all your help.

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

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

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

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

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

Hi Joseph,

I re installed nvda and did your suggestions about the add ons.  I still get version 8.

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

Hi Joseph,

When I press nvda shift plus 6 it says windows 8 64 bit.  I hope this helps.

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

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

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



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

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.

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.

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.

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.