Date   

Chrome And Edge Chromium problem

majno
 

Hello. There has been some Chromium update wich makes nvda non reads properly some sites. one of those sites is https://play.pokemonshowdown.com

This site shows dynamic text wich NVDA reads line by line. But since one or two weeks each time a new line is printed NVDA reads all lines making it imposible to use the chat section  or battle for example.

This problem probably is happening for other sites with dynamic content.

the problem run when using Chrome and Edge chromium, not with firefox. Also using NVDA and JAWS, but windows narrator still works fine.


Re: NVDA's Tiflotecnia Vocalizer stopoped working again

Gerardo Corripio
 

OK and now? What’s the next step? It’s been several years since I did this, thus any tips to activate?

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:59 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Hello!

 

Go to %appdata%\vocalizer-for-nvda and delete both files.

 

I have already increased your remaining activations counter.

 

Regards,

 

Rui Fontes

Tiflotecnia, Lda.

 

 

 

Às 21:50 de 11/03/2020, Gerardo Corripio escreveu:

sSame thing; I get the error that the license is not valid due to the activation file being damaged? But why or how? I just turned off and on my Laptop like usual! And again with the newest version of Vocalizer, whose log file says; I’ll post it in another message; this thing isn’t letting me paste in this one. BE on the lookout!

 

 

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:41 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Try using the new driver that Andrea gaves the link...

 

Regards,

 

Rui Fontes

 

Às 21:19 de 11/03/2020, Gerardo Corripio escreveu:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 

 

 


Re: NVDA's Tiflotecnia Vocalizer stopoped working again

Rui Fontes
 

Hello!


Go to %appdata%\vocalizer-for-nvda and delete both files.


I have already increased your remaining activations counter.


Regards,


Rui Fontes

Tiflotecnia, Lda.




Às 21:50 de 11/03/2020, Gerardo Corripio escreveu:

sSame thing; I get the error that the license is not valid due to the activation file being damaged? But why or how? I just turned off and on my Laptop like usual! And again with the newest version of Vocalizer, whose log file says; I’ll post it in another message; this thing isn’t letting me paste in this one. BE on the lookout!

 

 

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:41 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Try using the new driver that Andrea gaves the link...

 

Regards,

 

Rui Fontes

 

Às 21:19 de 11/03/2020, Gerardo Corripio escreveu:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 

 


Re: NVDA's Tiflotecnia Vocalizer stopoped working again

Gerardo Corripio
 

sSame thing; I get the error that the license is not valid due to the activation file being damaged? But why or how? I just turned off and on my Laptop like usual! And again with the newest version of Vocalizer, whose log file says; I’ll post it in another message; this thing isn’t letting me paste in this one. BE on the lookout!

 

 

 

                                                                                              Enviado desde Correo para Windows 10

 

De: Rui Fontes
Enviado: miércoles, 11 de marzo de 2020 03:41 p. m.
Para: nvda@nvda.groups.io
Asunto: Re: [nvda] NVDA's Tiflotecnia Vocalizer stopoped working again

 

Try using the new driver that Andrea gaves the link...

 

Regards,

 

Rui Fontes

 

Às 21:19 de 11/03/2020, Gerardo Corripio escreveu:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 

 


Re: NVDA's Tiflotecnia Vocalizer stopoped working again

Rui Fontes
 

Try using the new driver that Andrea gaves the link...


Regards,


Rui Fontes


Às 21:19 de 11/03/2020, Gerardo Corripio escreveu:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 


Vocaliser Driver Update

Andrea Sherry
 


Re: NVDA's Tiflotecnia Vocalizer stopoped working again

 

Could be a server issue.

I had this with code factory where the server went down and nothing worked till it came back.

I had to reactivate all my synths but lost nothing thank god.



On 12/03/2020 10:19 am, Gerardo Corripio wrote:

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 


NVDA's Tiflotecnia Vocalizer stopoped working again

Gerardo Corripio
 

Any hints what might have happened between yesterday and today that today when I turned on my Windows10, it came up talking via the Windows10 1Core voice? Aside from the error of Vocalizer, I’d get another one, that said that the license wasn’t valid etc., aside from the error that over at Tiflotecnia is trying to be fixed.

When I go into NVDA, Vocalizer does appear in the menu, bugt not within the Synthesizer menu via NVDA+Control+s? Here’s my log in case any of you guys know what might have happened? I’d like to get my vocalizer voices back!

INFO - __main__ (15:09:16.670) - MainThread (9736):

Starting NVDA version 2019.3.1

INFO - core.main (15:09:17.803) - MainThread (9736):

Config dir: C:\Users\gerac\AppData\Roaming\nvda

INFO - config.ConfigManager._loadConfig (15:09:17.803) - MainThread (9736):

Loading config: C:\Users\gerac\AppData\Roaming\nvda\nvda.ini

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Windows version 10.0.18363 workstation

INFO - core.main (15:09:18.076) - MainThread (9736):

Using Python version 3.7.5 (tags/v3.7.5:5c02a39a0b, Oct 14 2019, 23:09:19) [MSC v.1916 32 bit (Intel)]

INFO - core.main (15:09:18.076) - MainThread (9736):

Using comtypes version 1.1.7

INFO - core.main (15:09:18.076) - MainThread (9736):

Using configobj version 5.1.0 with validate version 1.0.1

WARNING - external:synthDrivers.vocalizer_expressive.storage._loadLicenseData (15:09:19.017) - MainThread (9736):

Couldn't automatically unpickle 'C:\\Users\\gerac\\AppData\\Roaming\\vocalizer-for-nvda\\activation.dat', trying manual method

ERROR - synthDriverHandler.setSynth (15:09:19.031) - MainThread (9736):

setSynth

Traceback (most recent call last):

  File "synthDriverHandler.pyc", line 103, in setSynth

  File "synthDriverHandler.pyc", line 76, in getSynthInstance

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\__init__.py", line 82, in __init__

    _vocalizer.initialize(self._onIndexReached)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 182, in initialize

    preInitialize()

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_vocalizer.py", line 164, in preInitialize

    platformDll.vplatform_GetInterfaces(byref(installResources), byref(platformResources))

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\synthDrivers\vocalizer_expressive\_veTypes.py", line 302, in veCheckForError

    raise VeError(result, "Vocalizer Error: %s: %x" %(func.__name__, result))

synthDrivers.vocalizer_expressive._veTypes.VeError: Vocalizer Error: vplatform_GetInterfaces: f5

INFO - synthDriverHandler.setSynth (15:09:19.236) - MainThread (9736):

Loaded synthDriver oneCore

INFO - core.main (15:09:19.526) - MainThread (9736):

Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 with six version 1.12.0

INFO - brailleInput.initialize (15:09:19.526) - MainThread (9736):

Braille input initialized

INFO - braille.initialize (15:09:19.526) - MainThread (9736):

Using liblouis version 3.10.0

INFO - braille.initialize (15:09:19.536) - MainThread (9736):

Using pySerial version 3.4

INFO - braille.BrailleHandler.setDisplayByName (15:09:19.546) - MainThread (9736):

Loaded braille display driver noBraille, current display has 0 cells.

INFO - core.main (15:09:19.901) - MainThread (9736):

Java Access Bridge support initialized

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:09:19.922) - _UIAHandler.UIAHandler.MTAThread (4260):

UIAutomation: IUIAutomation6

WARNING - external:vlc_settingsHandler.QTInterface._loadRecentFiles (15:09:22.659) - MainThread (9736):

Error: number of recent files  and time count are different

INFO - core.main (15:09:22.959) - MainThread (9736):

NVDA initialized

ERROR - external:globalPlugins.vocalizer_expressive_globalPlugin.LicenseRenewer._doRenew (15:09:23.596) - Thread-2 (2352):

Error renewing license.

Traceback (most recent call last):

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\__init__.py", line 142, in _doRenew

    newData = client.renew(number, token)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 60, in renew

    return self._do_request(url, data)

  File "C:\Users\gerac\AppData\Roaming\nvda\addons\vocalizer_expressive_driver\globalPlugins\vocalizer_expressive_globalPlugin\vocalizer_validation_client\client.py", line 32, in _do_request

    response = urllib.request.urlopen(request)

  File "urllib\request.pyc", line 222, in urlopen

  File "urllib\request.pyc", line 531, in open

  File "urllib\request.pyc", line 641, in http_response

  File "urllib\request.pyc", line 569, in error

  File "urllib\request.pyc", line 503, in _call_chain

  File "urllib\request.pyc", line 649, in http_error_default

urllib.error.HTTPError: HTTP Error 404: Not Found

 

                                                                                              Enviado desde Correo para Windows 10

 


Re: Possible issue with bash terminal in windows 10?

Mike Sedmak
 

I found the problem, it was not NVDA. Apparently a recent windows 10
update reset some of my ubuntu terminal settings including disabling
the ctrl-shift-v hotkey for paste.

Mike

On 3/10/20, Mike Sedmak <mcsedmak@...> wrote:
Has anyone else run into trouble using control+shift+V to paste copied
text into a bash linux subsystem terminal window in windows 10 after
upgrading to nvda 2019.3.1?

Note the linux subsystem uses a non-standard paste as control-v is
already used by the linux system.

Thanks,
Mike


Re: I think NVDA has a memory leak or something

 

Giles,

           Sorry.  The 1903 to 1909 feature update changed the build number from 18362 to 18363, respectively, which is an unusually small jump.  As soon as I see "1836" as the first four digits of build I think 1909 these days.   Usually the build numbers jump quite a bit further on feature updates, which makes it easier to remember which major build number and Windows 10 version number go together.

            In any case, anyone still on 1903 should force an update to 1909 at this point.  Microsoft cleared it for all machines a month or two ago, and if a machine hasn't self-updated to it by now that suggests some sort of hitch in the gitty-up of Windows Update.   Step-by-step:

Doing a Windows 10 Repair Install or Feature Update Using the Windows 10 ISO file

               It helps if everything is as up to date as it can be when attempting diagnostics.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363  

Power is being told you're not loved and not being destroyed by it.

       ~ Madonna

 

 


Re: I think NVDA has a memory leak or something

Giles Turnbull
 

No, Brian, I do not mean 1909! I copied the information from NVDA's speech viewer which was reporting the info from the winver app. I have just double checked it and it is still saying version 1903.

Giles


Re: NVDA ebooks: Is there one for Access?

Giles Turnbull
 

Hi Quentin,

I'd actually be quite interested in a guide to using Access with NVDA. I've just applied for a job that involves a lot of data analysis ... something I used to do with Access in my sighted days.

When I lived in America I worked at a call centre run by Association for the Blind and Visually Impaired in Rochester, NY, and they used Access to log calls. I was using JAWS then because that was what was installed, but an NVDA guide would be very helpful :)

Giles


Re: NVDA Startup Screen Options

Hicks Steven (CORNWALL IT SERVICES)
 

Hi,

 

If I click continue, it says it has actually saved but it doesn’t seem to change the settings on the logon screen.

Microsoft Windows 10 latest build and latest build of NVDA.

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sarah k Alawami
Sent: 10 March 2020 22:45
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Startup Screen Options

 

If you hit continue as admin, can you then save the settings to the start up screen? Also what version of nvda and windows are you using?

Blessings and happy Tuesday, and hope that helps

Sarah Alawami, owner of TFFP. . For more info go to our website.

to subscribe to the feed click here and you can also follow us on twitter

Our discord is where you will know when we go live on [twitch.](http://twitch.tv/ke7zum] Feel free to give the channel a follow and see what is up there.

For stream archives, products you can buy and more visit my main lbry page and my tffp lbry page

Finally, to become a patron and help support the podcast go here

On 10 Mar 2020, at 13:53, Hicks Steven (CORNWALL IT SERVICES) via Groups.Io wrote:

Hi friends,

 

I go in to settings in NVDA and use current settings at the start up screen as I have NVDA faster than default.

It says that it needs to be a admin logged on and I am a local admin.

It doesn’t seem to save the settings, anyone have any ideas as to what could be going on please?

 



********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.

For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail



********************************************************************************************************************

This message may contain confidential information. If you are not the intended recipient please inform the
sender that you have received the message in error before deleting it.
Please do not disclose, copy or distribute information in this e-mail or take any action in relation to its contents. To do so is strictly prohibited and may be unlawful. Thank you for your co-operation.

NHSmail is the secure email and directory service available for all NHS staff in England and Scotland. NHSmail is approved for exchanging patient data and other sensitive information with NHSmail and other accredited email services.

For more information and to find out how you can switch, https://portal.nhs.net/help/joiningnhsmail


Re: NVDA doesn't read context menu

=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Have tried several times.

On Wed, 11 Mar 2020, Quentin Christensen wrote:

Date: Wed, 11 Mar 2020 16:14:49 +1100
From: Quentin Christensen <quentin@...>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
Try the COM registration fixing tool.
On Wed, Mar 11, 2020 at 4:14 PM 高生旺 <coscell@...> wrote:
I've re-install nvda and not install any addons yet.
BTW, This problem was happened after uninstall office.
Although I reinstalled office still not solved it.

On Wed, 11 Mar 2020, Quentin Christensen wrote:

> Date: Wed, 11 Mar 2020 16:05:52 +1100
> From: Quentin Christensen <quentin@...>
> Reply-To: nvda@nvda.groups.io
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] NVDA doesn't read context menu
>
> Did you try restarting with add-ons disabled?
> The only other thing I can think to try is press NVDA+N then T for tools, then select and go through "COM Registration fixing tool".
>
> Failing all that, if you could capture a copy of your log at "Debug" level with add-ons disabled, and send it to me at info@....
>
> Regards
>
> Quentin.
>
> On Wed, Mar 11, 2020 at 3:55 PM 高生旺 <coscell@...> wrote:
>       Hello
>
>       I cannot access context menu on desktop, file explorer and notepad etc.
>       But some where can accessed such Microsof Word.
>       And windows+x menu and IE screen also cannot be accessed.
>       Thank you!
>
>       On Wed, 11 Mar 2020, Quentin Christensen wrote:
>
>       > Date: Wed, 11 Mar 2020 15:27:57 +1100
>       > From: Quentin Christensen <quentin@...>
>       > Reply-To: nvda@nvda.groups.io
>       > To: nvda@nvda.groups.io
>       > Cc: NVDA Official Group <nvda@groups.io>
>       > Subject: Re: [nvda] NVDA doesn't read context menu
>       >
>       > Hi,
>       > Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text
in Word,
>       (or notepad)? 
>       > Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?
>       >
>       > On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
>       >       Hi
>       >
>       >       The last Alpha and 2019.3.1 all do not read context menu.
>       >       Narrator can read it.
>       >       How can I do to fix this problem?
>       >
>       >       Cheers
>       >
>       >
>       >
>       >
>       >
>       > --
>       > 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
>       >
>       >
>       >
>
>
>
>
>
> --
> 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
>
>
>
--
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


Re: NVDA doesn't read context menu

Quentin Christensen
 

Try the COM registration fixing tool.


On Wed, Mar 11, 2020 at 4:14 PM 高生旺 <coscell@...> wrote:
I've re-install nvda and not install any addons yet.
BTW, This problem was happened after uninstall office.
Although I reinstalled office still not solved it.

On Wed, 11 Mar 2020, Quentin Christensen wrote:

> Date: Wed, 11 Mar 2020 16:05:52 +1100
> From: Quentin Christensen <quentin@...>
> Reply-To: nvda@nvda.groups.io
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] NVDA doesn't read context menu
>
> Did you try restarting with add-ons disabled?
> The only other thing I can think to try is press NVDA+N then T for tools, then select and go through "COM Registration fixing tool".
>
> Failing all that, if you could capture a copy of your log at "Debug" level with add-ons disabled, and send it to me at info@....
>
> Regards
>
> Quentin.
>
> On Wed, Mar 11, 2020 at 3:55 PM 高生旺 <coscell@...> wrote:
>       Hello
>
>       I cannot access context menu on desktop, file explorer and notepad etc.
>       But some where can accessed such Microsof Word.
>       And windows+x menu and IE screen also cannot be accessed.
>       Thank you!
>
>       On Wed, 11 Mar 2020, Quentin Christensen wrote:
>
>       > Date: Wed, 11 Mar 2020 15:27:57 +1100
>       > From: Quentin Christensen <quentin@...>
>       > Reply-To: nvda@nvda.groups.io
>       > To: nvda@nvda.groups.io
>       > Cc: NVDA Official Group <nvda@groups.io>
>       > Subject: Re: [nvda] NVDA doesn't read context menu
>       >
>       > Hi,
>       > Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text in Word,
>       (or notepad)? 
>       > Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?
>       >
>       > On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
>       >       Hi
>       >
>       >       The last Alpha and 2019.3.1 all do not read context menu.
>       >       Narrator can read it.
>       >       How can I do to fix this problem?
>       >
>       >       Cheers
>       >
>       >
>       >
>       >
>       >
>       > --
>       > 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
>       >
>       >
>       >
>
>
>
>
>
> --
> 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
>
>
>





--
Quentin Christensen
Training and Support Manager


Re: NVDA doesn't read context menu

=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

I've re-install nvda and not install any addons yet.
BTW, This problem was happened after uninstall office.
Although I reinstalled office still not solved it.

On Wed, 11 Mar 2020, Quentin Christensen wrote:

Date: Wed, 11 Mar 2020 16:05:52 +1100
From: Quentin Christensen <quentin@...>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA doesn't read context menu
Did you try restarting with add-ons disabled?
The only other thing I can think to try is press NVDA+N then T for tools, then select and go through "COM Registration fixing tool".
Failing all that, if you could capture a copy of your log at "Debug" level with add-ons disabled, and send it to me at info@....
Regards
Quentin.
On Wed, Mar 11, 2020 at 3:55 PM 高生旺 <coscell@...> wrote:
Hello

I cannot access context menu on desktop, file explorer and notepad etc.
But some where can accessed such Microsof Word.
And windows+x menu and IE screen also cannot be accessed.
Thank you!

On Wed, 11 Mar 2020, Quentin Christensen wrote:

> Date: Wed, 11 Mar 2020 15:27:57 +1100
> From: Quentin Christensen <quentin@...>
> Reply-To: nvda@nvda.groups.io
> To: nvda@nvda.groups.io
> Cc: NVDA Official Group <nvda@groups.io>
> Subject: Re: [nvda] NVDA doesn't read context menu
>
> Hi,
> Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text in Word,
(or notepad)? 
> Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?
>
> On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
>       Hi
>
>       The last Alpha and 2019.3.1 all do not read context menu.
>       Narrator can read it.
>       How can I do to fix this problem?
>
>       Cheers
>
>
>
>
>
> --
> 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
>
>
>
--
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


Re: NVDA doesn't read context menu

Quentin Christensen
 

Did you try restarting with add-ons disabled?

The only other thing I can think to try is press NVDA+N then T for tools, then select and go through "COM Registration fixing tool".

Failing all that, if you could capture a copy of your log at "Debug" level with add-ons disabled, and send it to me at info@....

Regards

Quentin.

On Wed, Mar 11, 2020 at 3:55 PM 高生旺 <coscell@...> wrote:
Hello

I cannot access context menu on desktop, file explorer and notepad etc.
But some where can accessed such Microsof Word.
And windows+x menu and IE screen also cannot be accessed.
Thank you!

On Wed, 11 Mar 2020, Quentin Christensen wrote:

> Date: Wed, 11 Mar 2020 15:27:57 +1100
> From: Quentin Christensen <quentin@...>
> Reply-To: nvda@nvda.groups.io
> To: nvda@nvda.groups.io
> Cc: NVDA Official Group <nvda@groups.io>
> Subject: Re: [nvda] NVDA doesn't read context menu
>
> Hi,
> Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text in Word, (or notepad)? 
> Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?
>
> On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
>       Hi
>
>       The last Alpha and 2019.3.1 all do not read context menu.
>       Narrator can read it.
>       How can I do to fix this problem?
>
>       Cheers
>
>
>
>
>
> --
> 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
>
>
>





--
Quentin Christensen
Training and Support Manager


Re: NVDA doesn't read context menu

=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Hello

I cannot access context menu on desktop, file explorer and notepad etc.
But some where can accessed such Microsof Word.
And windows+x menu and IE screen also cannot be accessed.
Thank you!

On Wed, 11 Mar 2020, Quentin Christensen wrote:

Date: Wed, 11 Mar 2020 15:27:57 +1100
From: Quentin Christensen <quentin@...>
Reply-To: nvda@nvda.groups.io
To: nvda@nvda.groups.io
Cc: NVDA Official Group <nvda@groups.io>
Subject: Re: [nvda] NVDA doesn't read context menu
Hi,
Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text in Word, (or notepad)? 
Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?
On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
Hi

The last Alpha and 2019.3.1 all do not read context menu.
Narrator can read it.
How can I do to fix this problem?

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


Re: NVDA doesn't read context menu

Quentin Christensen
 

Hi,

Where are you trying to access the context menu?  Is it just in one program, or everywhere, eg does it differ if you try to access a context menu on say an item on the desktop vs the context menu on selected text in Word, (or notepad)?  Are you using any add-ons - if you press NVDA+Q then down arrow to "Restart with add-ons disabled" does it make a difference?

On Wed, Mar 11, 2020 at 2:10 PM 高生旺 <coscell@...> wrote:
Hi

The last Alpha and 2019.3.1 all do not read context menu.
Narrator can read it.
How can I do to fix this problem?

Cheers





--
Quentin Christensen
Training and Support Manager


NVDA doesn't read context menu

=?ISO-2022-JP?Q?=1B$B9b=4082=22=1B=28J?=
 

Hi

The last Alpha and 2019.3.1 all do not read context menu.
Narrator can read it.
How can I do to fix this problem?

Cheers