Re: Problems with latest nvda and outlook 2016 and windows 10
Hi, No log fragment on freezes or restarts here. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Sam Bushman
Sent: Tuesday, March 13, 2018 2:39 PM To: nvda@nvda.groups.io Cc: 'Joseph Lee' <joseph.lee22590@...> Subject: [nvda] Problems with latest nvda and outlook 2016 and windows 10
Hi Joseph and All,
For some reason on certain messages in outlook 2016 when I press enter on a message to read it restarts outlook. This does not happen in JAWS but happens in NVDA. If I reboot the problem goes away for a while then comes back.
Please see my log for more info:
Thanks, Sam
INFO - __main__ (15:34:40.739): Starting NVDA INFO - core.main (15:34:41.114): Config dir: C:\Users\User\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:34:41.114): Loading config: C:\Users\User\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:34:41.176): NVDA version master-14940,e78e72f9 INFO - core.main (15:34:41.176): Using Windows version 10.0.16299 workstation INFO - core.main (15:34:41.176): Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:19:30) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:34:41.176): Using comtypes version 1.1.3 INFO - synthDriverHandler.setSynth (15:34:42.558): Loaded synthDriver eloquence INFO - core.main (15:34:42.558): Using wx version 3.0.2.0 msw (classic) INFO - brailleInput.initialize (15:34:42.563): Braille input initialized INFO - braille.initialize (15:34:42.563): Using liblouis version 3.3.0 INFO - braille.BrailleHandler.setDisplayByName (15:34:42.565): Loaded braille display driver noBraille, current display has 0 cells. WARNING - core.main (15:34:42.586): Java Access Bridge not available INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:34:42.592): UIAutomation: IUIAutomation3 INFO - external:globalPlugins.wintenObjs._UIAHandlerEx.UIAHandlerEx.MTAThreadFunc (15:34:42.760): UIAutomation: IUIAutomation5 INFO - core.main (15:34:42.946): NVDA initialized ERROR - RPC process 1196 (nvda_slave.exe) (15:34:49.489): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 91, in main File "comHelper.pyc", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyc", line 180, in GetActiveObject File "comtypes\__init__.pyc", line 1245, in GetActiveObject File "_ctypes/callproc.c", line 950, in GetResult WindowsError: [Error -2147221021] Operation unavailable INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:24.890): Developer info for navigator object: name: u'PCM Plus' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x06F797B0> Python class mro: (<class 'NVDAObjects.IAccessible.sysListView32.ListItem'>, <class 'NVDAObjects.behaviors.RowWithFakeNavigation'>, <class 'NVDAObjects.behaviors.RowWithoutCellObjects'>, <class 'NVDAObjects.IAccessible.sysListView32.ListItemWithoutColumnSupport'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: (0, 5, 120, 88) value: None appModule: <'explorer' (appName u'explorer', process ID 5576) at address 6d29e30> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.16299.15' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 65912 windowClassName: u'SysListView32' windowControlID: 1 windowStyle: 1442855744 windowThreadID: 5580 windowText: u'FolderView' displayText: u'PCM Plus' IAccessibleObject: <POINTER(IAccessible) ptr=0x8f91df0 at 6e43e90> IAccessibleChildID: 1 IAccessible event parameters: windowHandle=65912, objectID=-4, childID=1 IAccessible accName: u'PCM Plus' IAccessible accRole: ROLE_SYSTEM_LISTITEM IAccessible accState: STATE_SYSTEM_SELECTABLE, STATE_SYSTEM_SELECTED, STATE_SYSTEM_MULTISELECTABLE, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (19922950) IAccessible accDescription: exception: (-2147352573, 'Member not found.', (None, None, None, 0, None)) IAccessible accValue: None
|
|
Problems with latest nvda and outlook 2016 and windows 10
Sam Bushman
Hi Joseph and All,
For some reason on certain messages in outlook 2016 when I press enter on a message to read it restarts outlook. This does not happen in JAWS but happens in NVDA. If I reboot the problem goes away for a while then comes back.
Please see my log for more info:
Thanks, Sam
INFO - __main__ (15:34:40.739): Starting NVDA INFO - core.main (15:34:41.114): Config dir: C:\Users\User\AppData\Roaming\nvda INFO - config.ConfigManager._loadConfig (15:34:41.114): Loading config: C:\Users\User\AppData\Roaming\nvda\nvda.ini INFO - core.main (15:34:41.176): NVDA version master-14940,e78e72f9 INFO - core.main (15:34:41.176): Using Windows version 10.0.16299 workstation INFO - core.main (15:34:41.176): Using Python version 2.7.14 (v2.7.14:84471935ed, Sep 16 2017, 20:19:30) [MSC v.1500 32 bit (Intel)] INFO - core.main (15:34:41.176): Using comtypes version 1.1.3 INFO - synthDriverHandler.setSynth (15:34:42.558): Loaded synthDriver eloquence INFO - core.main (15:34:42.558): Using wx version 3.0.2.0 msw (classic) INFO - brailleInput.initialize (15:34:42.563): Braille input initialized INFO - braille.initialize (15:34:42.563): Using liblouis version 3.3.0 INFO - braille.BrailleHandler.setDisplayByName (15:34:42.565): Loaded braille display driver noBraille, current display has 0 cells. WARNING - core.main (15:34:42.586): Java Access Bridge not available INFO - _UIAHandler.UIAHandler.MTAThreadFunc (15:34:42.592): UIAutomation: IUIAutomation3 INFO - external:globalPlugins.wintenObjs._UIAHandlerEx.UIAHandlerEx.MTAThreadFunc (15:34:42.760): UIAutomation: IUIAutomation5 INFO - core.main (15:34:42.946): NVDA initialized ERROR - RPC process 1196 (nvda_slave.exe) (15:34:49.489): __main__.main: slave error Traceback (most recent call last): File "nvda_slave.pyw", line 91, in main File "comHelper.pyc", line 22, in _lresultFromGetActiveObject File "comtypes\client\__init__.pyc", line 180, in GetActiveObject File "comtypes\__init__.pyc", line 1245, in GetActiveObject File "_ctypes/callproc.c", line 950, in GetResult WindowsError: [Error -2147221021] Operation unavailable INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (15:35:24.890): Developer info for navigator object: name: u'PCM Plus' role: ROLE_LISTITEM states: STATE_FOCUSABLE, STATE_SELECTABLE, STATE_FOCUSED, STATE_SELECTED isFocusable: True hasFocus: True Python object: <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x06F797B0> Python class mro: (<class 'NVDAObjects.IAccessible.sysListView32.ListItem'>, <class 'NVDAObjects.behaviors.RowWithFakeNavigation'>, <class 'NVDAObjects.behaviors.RowWithoutCellObjects'>, <class 'NVDAObjects.IAccessible.sysListView32.ListItemWithoutColumnSupport'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'documentBase.TextContainerObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>) description: None location: (0, 5, 120, 88) value: None appModule: <'explorer' (appName u'explorer', process ID 5576) at address 6d29e30> appModule.productName: u'Microsoft\xae Windows\xae Operating System' appModule.productVersion: u'10.0.16299.15' TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'> windowHandle: 65912 windowClassName: u'SysListView32' windowControlID: 1 windowStyle: 1442855744 windowThreadID: 5580 windowText: u'FolderView' displayText: u'PCM Plus' IAccessibleObject: <POINTER(IAccessible) ptr=0x8f91df0 at 6e43e90> IAccessibleChildID: 1 IAccessible event parameters: windowHandle=65912, objectID=-4, childID=1 IAccessible accName: u'PCM Plus' IAccessible accRole: ROLE_SYSTEM_LISTITEM IAccessible accState: STATE_SYSTEM_SELECTABLE, STATE_SYSTEM_SELECTED, STATE_SYSTEM_MULTISELECTABLE, STATE_SYSTEM_FOCUSED, STATE_SYSTEM_FOCUSABLE, STATE_SYSTEM_VALID (19922950) IAccessible accDescription: exception: (-2147352573, 'Member not found.', (None, None, None, 0, None)) IAccessible accValue: None
|
|
Re: Copying the path to a file
JM Casey <crystallogic@...>
I’ve not experienced this. I somehow remember it wasn’t always a thing, but I’m certainly glad to be able to paste to command prompt nowadays.
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of erik burggraaf
Sent: March 13, 2018 1:19 PM To: nvda@nvda.groups.io Subject: Re: [nvda] Copying the path to a file
The Windows 10 command line will not let me paste anything from the clipboard into the terminal. Is anybody else having this issue? Otherwise, this command is completely useful, and exactly what I needed right now. Thanks for sending it along. On March 13, 2018 12:54:44 PM "JM Casey" <crystallogic@...> wrote:
|
|
Re: continuing research into Outlook 2016 crashes on Windows 7
Jonathan COHN
Joseph,
Thanks, pretty much confirms my guesses though I still have a long way to go before understanding all the components of NVDA. In any case, the control-1, control-2, and control-3 commands in current versions of Outlook at least cause Outlook to crash when NVDA is running, but not when JAWS is running. As you specified this seems to be an ongoing issue and was reported with XP and Outlook 2007 so has been going on for a while if not this specific case. I suppose I could install 365 on my testing Windows 10 VM and see if this is a issue directly related to bad UIA within Win7. I just hate to leave a bug alone when I have source code and can accurately reproduce at will.
Though right now I need to verify that our implementation of Keylock is fully WCAG compliant. So, I might have to stick this away for a weekend project.
Thanks,
Jonathan
From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Hi, I see. In short, from what I can tell, UIA bridge freezes when trying to obtain something from an app. There are numerous itHub issues regarding this problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io>
On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 1:16 PM To: nvda@nvda.groups.io Subject: Re: [nvda] continuing research into Outlook 2016 crashes on Windows 7
OK, not quite sure but since my first query did not provide any information I decided to plow ahead.
Basic information from logs are:
Next item in NVDA log is: DEBUGWARNING - watchdog._watcher (15:14:37.355):
Followed by a couple of WARNING - watchdog._watcher (15:14:52.367): Core frozen in stack:
WARNING - watchdog._watcher (15:15:07.414): Core frozen in stack
At which point NVDA stops talking. After getting speech back through another screen reder, Outlook has a not responding message.
When I did a switch from Calendar View to Messages view I also got a debug watch dog but NVDA seemed to be able to clear it out with the following: IO - inputCore.InputManager.executeGesture (15:14:12.845): Input: kb(desktop):control+1 DEBUGWARNING - watchdog._watcher (15:14:14.868): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.085): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled IO - inputCore.InputManager.executeGesture (15:14:15.493): Input: kb(desktop):NVDA+t DEBUGWARNING - watchdog._watcher (15:14:15.592): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.911): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled DEBUGWARNING - watchdog._watcher (15:14:16.437): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.974): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728967 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728905 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728906 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728901 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728907 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728908 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728909 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728910 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.977): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728911 and childID 0: [Error -2147467259] Unspecified error IO - speech.speak (15:14:19.016): Speaking [LangChangeCommand ('en_GB'), u'Inbox - jcohn@... - Outlook']
Trying to recover from freeze, core stack
From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Hi, In order to verify your claim, I need an evidence please. Cheers, Joseph
From:
nvda@nvda.groups.io
<nvda@nvda.groups.io>
On Behalf Of Cohn, Jonathan
OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I
So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?
Thanks!
Jonathan Cohn
|
|
Re: Other tool for solving the Verification Image
Mallard
I use Webvisum with a portable esr of version 52. Perfect. Free, and reliable.
toggle quoted messageShow quoted text
Ciao, Ollie
Il 13/03/2018 13:04, Chris via Groups.Io ha scritto:
|
|
Re: Other tool for solving the Verification Image
Mallard
Rumola never worked for me. When I installed it, on first attempt to solve a captcha, I was told I had no more free trials. onsense!
toggle quoted messageShow quoted text
Ciao, Ollie
Il 13/03/2018 13:40, P. Otter ha scritto:
hello there and is it known if rumola will work on the newest version of firefox?
|
|
Re: continuing research into Outlook 2016 crashes on Windows 7
Hi, I see. In short, from what I can tell, UIA bridge freezes when trying to obtain something from an app. There are numerous itHub issues regarding this problem. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 1:16 PM To: nvda@nvda.groups.io Subject: Re: [nvda] continuing research into Outlook 2016 crashes on Windows 7
OK, not quite sure but since my first query did not provide any information I decided to plow ahead.
Basic information from logs are:
Next item in NVDA log is: DEBUGWARNING - watchdog._watcher (15:14:37.355):
Followed by a couple of WARNING - watchdog._watcher (15:14:52.367): Core frozen in stack:
WARNING - watchdog._watcher (15:15:07.414): Core frozen in stack
At which point NVDA stops talking. After getting speech back through another screen reder, Outlook has a not responding message.
When I did a switch from Calendar View to Messages view I also got a debug watch dog but NVDA seemed to be able to clear it out with the following: IO - inputCore.InputManager.executeGesture (15:14:12.845): Input: kb(desktop):control+1 DEBUGWARNING - watchdog._watcher (15:14:14.868): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.085): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled IO - inputCore.InputManager.executeGesture (15:14:15.493): Input: kb(desktop):NVDA+t DEBUGWARNING - watchdog._watcher (15:14:15.592): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.911): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled DEBUGWARNING - watchdog._watcher (15:14:16.437): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.974): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728967 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728905 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728906 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728901 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728907 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728908 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728909 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728910 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.977): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728911 and childID 0: [Error -2147467259] Unspecified error IO - speech.speak (15:14:19.016): Speaking [LangChangeCommand ('en_GB'), u'Inbox - jcohn@... - Outlook']
Trying to recover from freeze, core stack
From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Hi, In order to verify your claim, I need an evidence please. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I
So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?
Thanks!
Jonathan Cohn
|
|
Re: continuing research into Outlook 2016 crashes on Windows 7
Jonathan COHN
OK, not quite sure but since my first query did not provide any information I decided to plow ahead.
Basic information from logs are:
Next item in NVDA log is: DEBUGWARNING - watchdog._watcher (15:14:37.355):
Followed by a couple of WARNING - watchdog._watcher (15:14:52.367): Core frozen in stack:
WARNING - watchdog._watcher (15:15:07.414): Core frozen in stack
At which point NVDA stops talking. After getting speech back through another screen reder, Outlook has a not responding message.
When I did a switch from Calendar View to Messages view I also got a debug watch dog but NVDA seemed to be able to clear it out with the following: IO - inputCore.InputManager.executeGesture (15:14:12.845): Input: kb(desktop):control+1 DEBUGWARNING - watchdog._watcher (15:14:14.868): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.085): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 894, in pumpAll File "IAccessibleHandler.pyo", line 617, in processGenericWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled IO - inputCore.InputManager.executeGesture (15:14:15.493): Input: kb(desktop):NVDA+t DEBUGWARNING - watchdog._watcher (15:14:15.592): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - core.CorePump.Notify (15:14:15.911): errors in this core pump cycle Traceback (most recent call last): File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 321, in _isUIAWindowHelper File "watchdog.pyo", line 195, in sendMessageCallCanceller CallCancelled DEBUGWARNING - watchdog._watcher (15:14:16.437): Trying to recover from freeze, core stack: File "nvda.pyw", line 212, in <module> File "core.pyo", line 473, in main File "wx\_core.pyo", line 8657, in MainLoop File "wx\_core.pyo", line 7952, in MainLoop File "core.pyo", line 443, in Notify File "IAccessibleHandler.pyo", line 880, in pumpAll File "IAccessibleHandler.pyo", line 654, in processFocusWinEvent File "IAccessibleHandler.pyo", line 521, in winEventToNVDAEvent File "_UIAHandler.pyo", line 327, in isUIAWindow File "_UIAHandler.pyo", line 315, in _isUIAWindowHelper
DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.974): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728967 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728905 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728906 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728901 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728907 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728908 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728909 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.976): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728910 and childID 0: [Error -2147467259] Unspecified error DEBUGWARNING - IAccessibleHandler.accessibleObjectFromEvent (15:14:18.977): oleacc.AccessibleObjectFromEvent with window 66464, objectID 100728911 and childID 0: [Error -2147467259] Unspecified error IO - speech.speak (15:14:19.016): Speaking [LangChangeCommand ('en_GB'), u'Inbox - jcohn@... - Outlook']
Trying to recover from freeze, core stack
From: <nvda@nvda.groups.io> on behalf of Joseph Lee <joseph.lee22590@...>
Hi, In order to verify your claim, I need an evidence please. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io>
On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 12:12 PM To: nvda@nvda.groups.io Subject: [nvda] continuing research into Outlook 2016 crashes on Windows 7
OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I
So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?
Thanks!
Jonathan Cohn
|
|
Re: Propellerhead reason accessibility
Tony Ballou
Hi Igor,
toggle quoted messageShow quoted text
Thanks for the info brother. That seems to be the case most of the time with programs like that, a real shame. Tony
On 3/9/2018 6:25 AM, Igor Kaplan wrote:
Hi Tony.
|
|
Re: say copy selected text
Tony Ballou
Hi,
There's an add on called clip speak, that will do this. I don't think its on the add ons website anymore though. I think because It works with windows 10 without a hitch that it should be; and I can drop box it too you if you like.
Tony
On 2/3/2018 1:38 PM, Kevin wrote:
|
|
Re: Blown away by the NVDA/MS Word tutorial!
Tony Ballou
Hi,
toggle quoted messageShow quoted text
Absolutely! There must haves for anyone who is in the teaching game or had a career in it at some point. And even if you're not, they are more than worth the investment. Tony
On 2/6/2018 12:35 PM, Ann Byrne wrote:
As a computer instructor, I have spent years looking for the best
|
|
Re: winamp with NVDA
Tony Ballou
Hi,
Yes it can. I believe there's an add on for it on the add ons website.
Tony
On 2/13/2018 2:27 PM, Kerryn Gunness via Groups.Io wrote:
|
|
Re: continuing research into Outlook 2016 crashes on Windows 7
Hi, In order to verify your claim, I need an evidence please. Cheers, Joseph
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Cohn, Jonathan
Sent: Tuesday, March 13, 2018 12:12 PM To: nvda@nvda.groups.io Subject: [nvda] continuing research into Outlook 2016 crashes on Windows 7
OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I
So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?
Thanks!
Jonathan Cohn
|
|
continuing research into Outlook 2016 crashes on Windows 7
Jonathan COHN
OK, some research makes me think that when I use the keyboard shortcut to change from Mailbox view to Calendar View in Outlook that the crash might be related to UIA not being handled correctly. Is there a way I could disable UIA for my copy of NVDA either in intirety or for Outlook just to execute this command without working with the NVDA core? I
So, could I write a Outlook addon that disables UIA when in the SuperGrid or in the INI files?
Thanks!
Jonathan Cohn
|
|
Re: Registry fixing tool in nvda
The feature is in the latest next snapshot.
On 3/13/2018 1:56 PM, Adriani Botez
wrote:
|
|
Re: where to find nvda tutorials
Tony Ballou
Hi,
Sorry for responding to this so late. Try this link.
http://www.josephsl.net/tutorials/
Also you can go to http://www.accessibilitycentral.net for more information and tutorials for NVDA and other programs.
Hope this helps.
Tony
On 3/1/2018 11:22 AM, Marisane Moruthanyana wrote:
|
|
Re: Gmail using thunderbird
Tony Ballou
Hi,
Sorry about getting to this so late. Yes, it certainly can. Once you install Thunderbird, when it prompts for adding an account, enter your Gmail account information and all should be gravy.
Tony
On 3/5/2018 7:57 PM, Arlene wrote:
|
|
Re: Registry fixing tool in nvda
Adriani Botez
Gene,
the feature is not in next yet, but it will be soon I guess. There are still some things to do.
Best Adriani
Von: nvda@nvda.groups.io <nvda@nvda.groups.io> Im Auftrag von Gene New Zealand
Hi Adriani Hopefully the snapshot fixes her problem. I am guessing hopefully she will let me ring her hopefully to a home number and guide her through the steps to get the snap shot etc and where to go in the menu etc.
On 3/13/2018 2:55 PM, Adriani Botez wrote:
--
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.
|
|
Re: Copying the path to a file
Hareth
Erik,
Win10 both command prompt and power shell does let you paste text in to via the ctrl plus V unless you've opened an other interface within the command line it self E.G android "ADB shell" interface, in that case you still able to paste following these steps": In the command interface press ALT plus space bar , then the letter "E" select the edit operation you want to do like select all, copy, and paste, ETC, from that sub menu and hit inter. Done Take care.
|
|
Re: Copying the path to a file
erik burggraaf <erik@...>
The Windows 10 command line will not let me paste anything from the clipboard into the terminal. Is anybody else having this issue? Otherwise, this command is completely useful, and exactly what I needed right now. Thanks for sending it along.
On March 13, 2018 12:54:44 PM "JM Casey" <crystallogic@...> wrote:
|
|