Re: Programming Braille Displays
Rui Fontes
Have you tried in Manage Input gestures dialog?
toggle quoted messageShow quoted text
Rui Fontes Às 09:13 de 01/12/2019, Pele West escreveu:
Hi Everyone
|
|
Re: accessing embedded video links in Power point slides
Payal Kapoor
hi Quentin,
toggle quoted messageShow quoted text
here is my response to the questions you've asked. thought i'd break them up into two parts. Q: When you say link to a video, do you mean a text URL or link on the slide, or do you mean an embedded video? When you activate a link it will open your browser to the specified URL. An embedded video has a preview of the video (a still image, similar to that shown on thumbnails in Youtube etc) with a triangle play button), when you activate it, the video plays there in the slideshow without opening another program. P: There is no real text link, only some image and text saying video. when coppied on to a word doc, it says hyperlink, but, no real URL. i am not sure what that would be ccalled. it is however, not an external source, but links to a folder that has all the relevant videos. i was told it links there and plays. essentially, it is an entire presentation made by sighted folk at my work place that is used for training. i am the first blind person attempting to use it. it contains two different PPTs for two different programmes we run. also, it has other training material we access from within the whole thing. Q: Activating links is a bit problematic and sounds like what you are encountering. To activate a link on a slide, press TAB to move to it - NVDA reports nothing - and then press ENTER. Out of curiosity, since you mentioned trying it with Jaws, did you have trouble with Jaws as well? (That would help narrow down the issue - if it works fine with Jaws, it could be NVDA not responding correctly to the link - if it doesn't work any better with Jaws then it's more likely to be PowerPoint not exposing it correctly). P: I think what you have said about the problem with accessing links is exactly what i'm having trouble with. however, i noticed that when the PPT is in slide mode, where more specifically, i activate the edit mode by pressing enter when in the specific slide, the link appears alongside the video. arrow down to it, choosing the open hyperlink option in the applications menu, voila! the video began playing. i was told that this option cannot be used when making a presentation, since it is not visually appealing or as good as it is in the presentation mode. the presentation mode won't show me a link,and when pressing enter there brings a prompt saying-no pointer available; choose a pointer. back to the application menu, but this time, all the pointer options do nothing. JAWS did nothing different either. in fact, NVDA allowed me to see the link; JAWS didn't. that might also be due to the old version of JAWS i have installed on my laptop. also, could you tell me how can i copy the contents of the slides, so i have it in a word doc to refer as notes rather than opepning the PPT eacj time? i did try the universal copy paste command, but strangely nothing showed up. this is definitely a deterrent in being able to run presentations visually for sighted folk when training. i hope we find a resolution to it soon enough. thanks for the help. Best, Payal
On 12/2/19, Quentin Christensen <quentin@nvaccess.org> wrote:
When you say link to a video, do you mean a text URL or link on the slide,
|
|
Re: Typhoon
Betsy Grenevitch
I will be praying for you and your family. Please somehow let us know how things are going there. I hope they allow this topic to continue since it is affecting one of the list members.
On 12/1/2019 3:17 PM, Arlene wrote:
-- Betsy Grenevitch 678=862-3876
|
|
Re: Typhoon
Sile
Thinking of you and your family at this time.
On Dec 1, 2019, at 8:19 AM, molly the blind tech lover <brainardmolly@gmail.com> wrote:Sile
|
|
Re: Nvda keeps repeating every thing twice on the whats new page with alpha.
Kevin Cussick
as I say using firefox and edge dev. happens with both.
toggle quoted messageShow quoted text
On 30/11/2019 23:47, Quentin Christensen wrote:
As Joseph said, which browser are you using?
|
|
Re: accessing embedded video links in Power point slides
Quentin Christensen
When you say link to a video, do you mean a text URL or link on the slide, or do you mean an embedded video? When you activate a link it will open your browser to the specified URL. An embedded video has a preview of the video (a still image, similar to that shown on thumbnails in Youtube etc) with a triangle play button), when you activate it, the video plays there in the slideshow without opening another program. While running the slideshow, activating embedded videos should work ok. Activating links is a bit problematic and sounds like what you are encountering. To activate a link on a slide, press TAB to move to it - NVDA reports nothing - and then press ENTER. Out of curiosity, since you mentioned trying it with Jaws, did you have trouble with Jaws as well? (That would help narrow down the issue - if it works fine with Jaws, it could be NVDA not responding correctly to the link - if it doesn't work any better with Jaws then it's more likely to be PowerPoint not exposing it correctly). Re obscured, that is usually reported at design time (ie when you open the file in PowerPoint but haven't pressed F5 to run the slideshow). and means that one placeholder is covering another on the slide. It may not mean the contents of each aren't visible - if you have a one line title, but expand the size of the placeholder to cover the whole slide, it won't actually hide any other content but it will announce that it is covering it (and that the other content is obscured). Overlapping placeholders can also be used for visual effect, although in general, when creating, it is safest to try to avoid overlapping unless you are sure of what you are doing. If you want to activate a link within a placeholder at design time, you can move to it, then open the context menu and select "Open link". We do have an issue for the problem with links while running slideshows here: https://github.com/nvaccess/nvda/issues/7288 Feel free to add any extra comments on that (if you do, the issue is still present in the latest alpha). Regards Quentin.
On Mon, Dec 2, 2019 at 2:02 AM Payal Kapoor <payal69@...> wrote: hi, --
Quentin Christensen Training and Support Manager 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 keeps repeating every thing twice on the whats new page with alpha.
Kevin Cussick
edge dev and firefox I am sure I already said this but maybe not.
toggle quoted messageShow quoted text
On 29/11/2019 23:18, Joseph Lee wrote:
Hi,
|
|
Re: NVDA not reading MS-Word Dialog Boxes
Quentin Christensen
Try running the "COM Registration fixing tool" which you can find on NVDA's tools menu (NVDA+N, then T, then down arrow to that option and enter). Otherwise, please let us know exactly WHICH version of Windows / office the machines are running. A copy of the NVDA log from one of the affected machines might also help (either pasted into the body of a message, or email oflist to info@... with a quick description of the issue). See: https://github.com/nvaccess/nvda/wiki/LogFilesAndCrashDumps for info on the log, debug level would be ideal. Regards Quentin
On Mon, Dec 2, 2019 at 2:56 AM Aman Agrawal <amanagrawal456@...> wrote:
--
Quentin Christensen Training and Support Manager 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: Why does NVDA say selected instead at times?
Gene
Perhaps. I wonder if this is information
Microsoft is presenting. It doesn't sound like something NVDA would
do.
I should correct an error. I initially said
the run dialog presents a list. It’s a combo box but it evidently is not a
standard one. I don't know how they look but combo boxes don't usually
announce items as selected.
Gene
----- Original Message -----
From: Laughing Thunder
Sent: Sunday, December 01, 2019 2:48 PM
Subject: Re: [nvda] Why does NVDA say selected instead at
times? I actually have no idea. Perhaps someone else with more knowledge on that
side of things can explain. On 12/1/2019 4:55 AM, Gene wrote:
-- Laughingthunder
|
|
Re: Why does NVDA say selected instead at times?
Laughing Thunder
I actually have no idea. Perhaps someone else with more knowledge
on that side of things can explain.
On 12/1/2019 4:55 AM, Gene wrote:
--
Laughingthunder
|
|
Re: Typhoon
Arlene
toggle quoted messageShow quoted text
From: Jaffar Sidek
Sent: December 1, 2019 5:10 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.
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Well its in alpha right now. And unless you want to modify manafests to get addons installed which who knows for the older stuff I may just do that and hope they work, I wouldn't jump the gun right now. The big reason is its just like to close to the end of the year and its not quite ready. At any rate, I usually try to lock down all machines, and don't update things on christmas day. We have the last big update to windows in the next couple weeks.
On 2/12/2019 7:43 am, Mike Capelle
wrote:
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Mike Capelle <mcap@...>
No the alpha or beta of 19.3, because I am using development apps, and it says tested with NVDA 19.3.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Brian Vogel
On Sun, Dec 1, 2019 at 01:50 PM, Mike Capelle wrote:
The latest released version of NVDA is 2019.2.1. Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Mike Capelle <mcap@...>
Thanks so much for this.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Sent: Sunday, December 1, 2019 12:53 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi, NVDA 2019.3 stable version is not available yet, but the alpha snapshots are (I don’t recommend using alpha builds unless you are ready to provide feedback or deal with bleeding-edge code). The message about add-ons might be due to you checking for development releases. I’ll make a general community announcement about it in the coming hours. Cheers, Joseph From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mike Capelle
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
Community add-ons and NVDA 2019.3 update: live development snapshots
Hi NVDA users,
As some of you may have noticed, certain builds of various community add-ons will advertise themselves as compatible with or requiring NVDA 2019.3 in any form. This is because several of us are releasing live development snapshots to test how add-ons are doing in the real world. This is typically done via development snapshots, but I know that some stable releases do contain code that will function in old and new NVDA releases.
Answers to some frequently asked questions:
Q. When I try to install an add-on, NVDA says “minimum version: 2019.3”.
Some add-ons (especially recent development snapshots) do require NVDA 2019.3 as they utilize code introduced in this release (not just Python 3).
Q. I have 2019.3 alpha and an add-on update says it is not compatible.
At least one add-on is retiring (or is end of life) as features from it are part of NVDA.
Q. I’m using Add-on Updater. I recently updated to a dev version yet Add-on Updater wants to download an old release.
This is due to add-on files database records. If you run into this, disable update check for affected add-ons (NVDA menu/Preferences/Settings/Add-on Updater/Do not update add-ons list and check ones you don’t want to get updates).
Q. I’m using NVDA 2019.2.1 with Add-on Updater installed, and when I check for updates, I get an update that isn’t compatible with the version I’m using.
You need to switch to stable channel for the time being (NVDA menu/Preferences/Settings/Add-on Updater/Prefer development releases, uncheck add-ons that you wish to switch to stable channel).
Q. What if my add-on is not listed n Add-on Updater?
Not all add-on updates can be checked via Add-on Updater (many speech synthesizers are excluded form update checks). The best course of action is contacting add-on authors about compatibility of these add-ons.
Q. I wish to report compatibility status of some add-ons.
Please do so if and only if you have absolutely latest releases and you are confident that the add-on in question is indeed incompatible in some way.
For people using my add-ons: for people using development snapshots of various add-ons, recent and upcoming snapshots will require NVDA 2019.3 in order to function. This is done to test how my add-ons are doing in the real world, and only after going through testing will they graduate to stable channel (this will happen after 2019.3 beta or RC is released).
Cheers, Joseph
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Hi, NVDA 2019.3 stable version is not available yet, but the alpha snapshots are (I don’t recommend using alpha builds unless you are ready to provide feedback or deal with bleeding-edge code). The message about add-ons might be due to you checking for development releases. I’ll make a general community announcement about it in the coming hours. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Mike Capelle
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
On Sun, Dec 1, 2019 at 01:50 PM, Mike Capelle wrote:
Where do I get 19.3 of NVDA?The latest released version of NVDA is 2019.2.1. -- Brian - Windows 10 Pro, 64-Bit, Version 1909, Build 18363 Most of the change we think we see in life is due to truths being in and out of favor. ~ Robert Frost, The Black Cottage (1914)
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Mike Capelle <mcap@...>
Where do I get 19.3 of NVDA? Most of my apps/addons wont work, it says I need 19.3.
|
|
Re: Typhoon
Rosemarie Chavarria
I'll be praying for you too. I've heard those typhoons are really awful.
toggle quoted messageShow quoted text
On 12/1/2019 5:18 AM, molly the blind tech lover wrote:
I will be praying for you. God bless you and your family.
|
|
Re: Windows 10 App Essentials 19.11.3
#addonrelease
Gary Metzler
toggle quoted messageShow quoted text
From: Joseph Lee
Sent: Sunday, December 1, 2019 10:30 AM To: nvda@nvda.groups.io Subject: Re: [nvda] Windows 10 App Essentials 19.11.3 #AddonRelease
Hi, Glad it is resolved for you. Let us know if you run into other issues in the future. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a reset of my windows and now I get the right version number. Thanks for all your help.
Sent from Mail for Windows 10
From: Joseph Lee
Hi, Try going to addons.nvda-project.org. I think this issue is way beyond add-ons – it is NVDA compatibility mode problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
For some reason I can’t get to the nvda add on page. I want to show the ms tech the problem I am having How can I get to the add on page? Thanks for any help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Complete reset as in performing a Windows 10 reset with no user data left. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee via Groups.Io
Hi, At this point, I’m out of options except for a complete reset. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I did a repair last night but,it didn’t help. Thanks for all your help.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, this confirms the suspicion that somehow NVDA is told to run in compatibility mode when installed. If removing and reinstalling NVDA from scratch (including via portable copy) doesn’t work, chances are that this might be a registry issue that is way beyond our control. The most effective way to resolve this (apart from changing compatibility mode settings, which might be something not many people are familiar with) is a non-destructive Windows 10 reinstall using Media Creation Tool for Version 1909. Failing that, a reset might be in order (you must reinstall desktop apps including NVDA if you decide to go down this path). Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I ran the portable copy and installed from there but, I still get version 8 .
Here is the log:
INFO - __main__ (15:33:23.819): Starting NVDA INFO - core.main (15:33:24.457): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:33:24.457): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:33:24.829): NVDA version 2019.2.1 INFO - core.main (15:33:24.829): Using Windows version 6.2.9200 workstation INFO - core.main (15:33:24.829): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:33:24.829): Using comtypes version 1.1.7 INFO - core.main (15:33:24.829): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (15:33:25.956): No touch devices found DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (15:33:28.309): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (15:33:28.362): Loaded synthDriver oneCore DEBUGWARNING - core.main (15:33:28.362): Slow starting core (6.32 sec) DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (15:33:28.362): No CLDR data for locale en_US INFO - core.main (15:33:28.980): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (15:33:28.980): Braille input initialized INFO - braille.initialize (15:33:28.980): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (15:33:28.996): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:33:29.346): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (15:33:29.818): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (15:33:29.947): No touch devices found DEBUGWARNING - Python warning (15:33:34.384): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (15:33:34.607): NVDA initialized DEBUGWARNING - watchdog._watcher (15:34:17.881): Trying to recover from freeze, core stack: File "nvda.pyw", line 231, in <module> File "core.pyo", line 519, in main File "wx\core.pyo", line 2134, in MainLoop File "gui\__init__.pyo", line 1003, in Notify File "core.pyo", line 490, in run File "queueHandler.pyo", line 86, in pumpAll File "queueHandler.pyo", line 53, in flushQueue File "eventHandler.pyo", line 62, in _queueEventCallback File "eventHandler.pyo", line 150, in executeEvent File "eventHandler.pyo", line 163, in doPreGainFocus File "api.pyo", line 107, in setFocusObject File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\__init__.pyo", line 501, in _get_container File "baseObject.pyo", line 47, in __get__ File "baseObject.pyo", line 147, in _getPropertyViaCache File "NVDAObjects\IAccessible\__init__.pyo", line 962, in _get_parent File "NVDAObjects\__init__.pyo", line 78, in __call__ File "NVDAObjects\IAccessible\__init__.pyo", line 649, in __init__ File "comtypes\__init__.pyo", line 1160, in QueryInterface
ERROR - RPC process 3228 (nvda_slave.exe) (15:34:20.319): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 93, in main File "comHelper.pyo", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyo", line 180, in GetActiveObject File "comtypes\__init__.pyo", line 1247, in GetActiveObject File "_ctypes/callproc.c", line 946, in GetResult WindowsError: [Error -2147221021] Operation unavailable DEBUGWARNING - Python warning (15:34:20.404): C:\Program Files (x86)\NVDA\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (15:34:21.678): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) DEBUGWARNING - Python warning (15:35:48.522): C:\Program Files (x86)\NVDA\library.zip\keyboardHandler.py:528: DeprecationWarning: Yield() is deprecated INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:58.546): Developer info for navigator object: name: u'Message' role: ROLE_EDITABLETEXT states: STATE_FOCUSABLE, STATE_MULTILINE, STATE_FOCUSED isFocusable: True hasFocus: True Python object: <nvdaBuiltin.appModules.outlook.OutlookWordDocument object at 0x0A624ED0> Python class mro: (<class 'nvdaBuiltin.appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.winword.WordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: RectLTWH(left=7, top=252, width=1569, height=600) value: None appModule: <'outlook' (appName u'outlook', process ID 1536) at address a5e55f0> appModule.productName: u'Microsoft Outlook' appModule.productVersion: u'16.0.12130.20390' TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'> windowHandle: 787432 windowClassName: u'_WwG' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 16 windowThreadID: 3532 windowText: u'Message' displayText: u'' IAccessibleObject: <POINTER(IAccessible) ptr=0x5f6b2a8 at a5d1170> IAccessibleChildID: 0 IAccessible event parameters: windowHandle=787432, objectID=-4, childID=0 IAccessible accName: u'Message' IAccessible accRole: ROLE_SYSTEM_CLIENT IAccessible accState: STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (1048580) IAccessible accDescription: None IAccessible accValue: None
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Yep, sounds like the installed copy got compatibility mode set. Can you install this portable copy and see if that makes a difference? To do so, run the portable copy, then to go NVDA menu/Tools/Install. Do not check the box for copying portable config to installed version. Say “yes” when User Account Control (UAC) appears, and when “success” message shows up, press Enter to start the installed copy. Then with the installed copy running, open log viewer and send me the beginning part of the log as a reply, as it’ll confirm if indeed this resolved it or NVDA still set to run in compatibility mode. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I created a portable copy and the windows version was 10. Here is the log: INFO - __main__ (13:43:37.826): Starting NVDA INFO - core.main (13:43:38.128): Config dir: C:\Users\Owner\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (13:43:38.128): Loading config: C:\Users\Owner\AppData\Roaming\nvda\nvda.ini INFO - core.main (13:43:38.529): NVDA version 2019.2.1 INFO - core.main (13:43:38.529): Using Windows version 10.0.18363 workstation INFO - core.main (13:43:38.529): Using Python version 2.7.16 (v2.7.16:413a49145e, Mar 4 2019, 01:30:55) [MSC v.1500 32 bit (Intel)] INFO - core.main (13:43:38.529): Using comtypes version 1.1.7 INFO - core.main (13:43:38.529): Using configobj version 5.1.0 with validate version 1.0.1 DEBUGWARNING - touchHandler.touchSupported (13:43:38.809): Touch only supported on installed copies DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_GeorgeM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_SusanM, WindowsError(2, 'The system cannot find the file specified') DEBUGWARNING - synthDrivers.oneCore.SynthDriver._isVoiceValid (13:43:39.549): Could not open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Speech_OneCore\Voices\Tokens\MSTTS_V110_enGB_HazelM, WindowsError(2, 'The system cannot find the file specified') INFO - synthDriverHandler.setSynth (13:43:39.575): Loaded synthDriver oneCore INFO - core.main (13:43:39.575): Using wx version 4.0.3 msw (phoenix) wxWidgets 3.0.5 INFO - brailleInput.initialize (13:43:39.579): Braille input initialized INFO - braille.initialize (13:43:39.585): Using liblouis version 3.10.0 INFO - braille.BrailleHandler.setDisplayByName (13:43:39.595): Loaded braille display driver noBraille, current display has 0 cells. INFO - _UIAHandler.UIAHandler.MTAThreadFunc (13:43:39.930): UIAutomation: IUIAutomation6 DEBUGWARNING - inputCore.InputManager.loadLocaleGestureMap (13:43:40.165): No locale gesture map for language en DEBUGWARNING - touchHandler.touchSupported (13:43:40.288): Touch only supported on installed copies DEBUGWARNING - Python warning (13:43:44.013): C:\Users\Owner\AppData\Roaming\nvda\addons\remote\globalPlugins\remoteClient\configuration.py:5: DeprecationWarning: Importing validate directly is deprecated. Please use configobj.validate instead INFO - core.main (13:43:44.352): NVDA initialized DEBUGWARNING - characterProcessing._getSpeechSymbolsForLocale (13:43:44.553): No CLDR data for locale en_US DEBUGWARNING - Python warning (13:43:45.071): C:\Users\Owner\AppData\Local\Temp\nsc86E4.tmp\app\library.zip\api.py:274: DeprecationWarning: Yield() is deprecated DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (13:43:56.013): accRole failed: (-2147024809, 'The parameter is incorrect.', (None, None, None, 0, None)) INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:44:23.746): Developer info for navigator object: name: u'nvda_2019.2.1.exe' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.Dynamic_UIItemListItemUIA object at 0x055ED030> Python class mro: (<class 'NVDAObjects.Dynamic_UIItemListItemUIA'>, <class 'NVDAObjects.UIA.UIItem'>, <class 'NVDAObjects.UIA.ListItem'>, <class 'NVDAObjects.UIA.UIA'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: '' location: RectLTWH(left=460, top=591, width=478, height=22) value: '' appModule: <'explorer' (appName u'explorer', process ID 1828) at address 501e6f0> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.18362.1' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 459738 windowClassName: u'DirectUIHWND' windowControlID: 0 windowStyle: 1442840576 extendedWindowStyle: 0 windowThreadID: 728 windowText: u'' displayText: u'nvda_2019.2.1.exe 11/ 28/ 2019 6:33 PM 23,830 KB' UIAElement: <POINTER(IUIAutomationElement) ptr=0x8d77b88 at 5597c10> UIA automationID: 515 UIA frameworkID: DirectUI UIA runtimeID: (1828, 254995280, 0) UIA providerDescription: [pid:1828,providerId:0x0 Main(parent link):Unidentified Provider (unmanaged:explorerframe.dll)] UIA className: UIItem UIA patterns available: LegacyIAccessiblePattern, InvokePattern, ScrollItemPattern, SelectionItemPattern, ValuePattern
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, If so, I’m afraid that this is beyond my area. Let’s try one more step:
Paste the log fragment as a reply to this email so Quentin and I can figure out exactly what is up. If Windows version line says “10.0.18363”, chances are that it is specific to the installed version; if it says “6.2.9200”, chances are that it is unique to your computer. If so, I advise a non-destructive feature update reinstallation – download Media Creation Tool for 1909, create an ISO, open the resulting ISO file, run setup.exe, and tell the installer to upgrade while keeping everything. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
I re installed nvda and did your suggestions about the add ons. I still get version 8.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, Ah, this explains it – somehow, NVDA was told to run in compatibility mode. Without intervention, Python 2.7 will assume it is running on Windows 8 when in fact you might be using Windows 10. Can you try the following for me:
If OneCore comes up, restart NVDA with partial add-on functionality. To do so:
If this does not help, reinstall NVDA from scratch. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Joseph,
When I press nvda shift plus 6 it says windows 8 64 bit. I hope this helps.
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Joseph Lee
Hi, You may need to manually type these lines into Python Console. Another approach: if you have Resource Monitor (hopefully latest stable release), press NVDA+Shift+Number row 6 and see what NVDA says about Windows version. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Gary Metzler
Hi Jacob,
What I did was copy and paste the lines just as Joseph typed them.
Jacob Kruger +2782 413 4791 "Resistance is futile...but, acceptance is versatile..." On 2019-11-28 10:23 AM, Gary Metzler wrote:
|
|