NVDA Issues with Outlook 2016


Sam Bushman
 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi all,

I and Sam have been troubleshooting this for a while with no concrete solutions so far. Can others help Sam please also?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Jonathan Milam
 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Jonathan Milam
 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Sam Bushman
 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Jonathan Milam
 

I began using NVDA with 2017.1, so I’m not sure about 2016.4 but I would assume it would be the same for me.  Interestingly enough, with 2017.1 and .2, I didn’t get any error messages but had the sluggishness.  The errors started with the Next version nvda_snapshot_try-noGetPixel-14093,ad84027c.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Jonathan Milam
 

Yeah they do.  I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

This leads me to believe that a call to Microsoft might be in order: something odd is going on with one or more NVDA components, an issue with Outlook, one or more DLL’s being unregistered or something else. Once I get confirmation from others, I’ll forward our findings to developers for further analysis.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Yeah they do.  I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Sam Bushman
 

I have also ran with out any addons and same thing.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 1:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Yeah they do.  I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

Okay, this narrows the problem a bit. So we the developers will need to decide between keeping NVDA running fast with the noPixel patch applied, or deal with slower performance with no errors. Both situations aren’t ideal at this point.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:46 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

I began using NVDA with 2017.1, so I’m not sure about 2016.4 but I would assume it would be the same for me.  Interestingly enough, with 2017.1 and .2, I didn’t get any error messages but had the sluggishness.  The errors started with the Next version nvda_snapshot_try-noGetPixel-14093,ad84027c.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


Sam Bushman
 

Please test and look at your nvda log, because for me this has happened through all updates.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, this narrows the problem a bit. So we the developers will need to decide between keeping NVDA running fast with the noPixel patch applied, or deal with slower performance with no errors. Both situations aren’t ideal at this point.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:46 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

I began using NVDA with 2017.1, so I’m not sure about 2016.4 but I would assume it would be the same for me.  Interestingly enough, with 2017.1 and .2, I didn’t get any error messages but had the sluggishness.  The errors started with the Next version nvda_snapshot_try-noGetPixel-14093,ad84027c.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Hi,

The thing is, I cannot reproduce errors folks are describing with Outlook 2016 at the moment.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:53 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Please test and look at your nvda log, because for me this has happened through all updates.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:52 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, this narrows the problem a bit. So we the developers will need to decide between keeping NVDA running fast with the noPixel patch applied, or deal with slower performance with no errors. Both situations aren’t ideal at this point.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:46 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

I began using NVDA with 2017.1, so I’m not sure about 2016.4 but I would assume it would be the same for me.  Interestingly enough, with 2017.1 and .2, I didn’t get any error messages but had the sluggishness.  The errors started with the Next version nvda_snapshot_try-noGetPixel-14093,ad84027c.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:44 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

They have all had the same errors, this has been happening to me for ever.

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Joseph,

 

I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.

 

Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016

 

Hi Sam,

 

I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.


Jonathan

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io
Subject: [nvda] NVDA Issues with Outlook 2016

 

Hi All,

 

I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.

 

INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

  File "nvda_slave.pyw", line 90, in main

  File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

  File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

  File "comtypes\__init__.pyc", line 1165, in GetActiveObject

  File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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

 

 

 

Thank you,

Sam

 


 

Well to be honest, I had a similar issue once, if you have adobe reader dc you maybe able to temperarily fix it by doing a repair install, however every update to office in my case broke it again.

Eventually on the system with the issue I installed another version of office and it was fine though its still got some issues.

The box is quite old so eventually I will replace it.

On my other workstation I have had this issue, after my experience with microsoft, I simply just did a reformat and the problem went away.

On that note if you use registry cleaners including ccleaner then you probably hosed your system and probably should just reinstall windows.

I havn't needed to run mine for ages, and windows at least 10 anyway does a good job of clearing its own trash.

On 14/06/2017 7:49 a.m., Joseph Lee wrote:
Hi,

This leads me to believe that a call to Microsoft might be in order: something odd is going on with one or more NVDA components, an issue with Outlook, one or more DLL’s being unregistered or something else. Once I get confirmation from others, I’ll forward our findings to developers for further analysis.

Cheers,

Joseph


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Yeah they do. I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


They have all had the same errors, this has been happening to me for ever.

Sam



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi Joseph,


I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors. However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi Sam,


I am having the exact same issues. At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist. I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs. I don’t get it.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA Issues with Outlook 2016


Hi All,


I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.


INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

File "nvda_slave.pyw", line 90, in main

File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

File "comtypes\__init__.pyc", line 1165, in GetActiveObject

File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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




Thank you,

Sam





Gene
 

A registry cleaner may cause damage and they usually don't improve performance.  But the CCleaner registry Cleaner is considered pretty safe by the advisors I read on the subject.  If a problem actually might be a registry problem, running a cleaner and not using aggressive settings might help, then again, it might not and it might cause other problems.  But if you aren't having such a problem, running a cleaner introduces a certain amount of risk and no benefits. 
 
Gene

----- Original Message -----
Sent: Tuesday, June 13, 2017 4:16 PM
Subject: Re: [nvda] NVDA Issues with Outlook 2016

Well to be honest, I had a similar issue once, if you have adobe reader
dc you maybe able to temperarily fix it by doing a repair install,
however every update to office in my case broke it again.

Eventually on the system with the issue I installed another version of
office and it was fine though its still got some issues.

The box is quite old so eventually I will replace it.

On my other workstation I have had this issue, after my experience with
microsoft, I simply just did a reformat and the problem went away.

On that note if you use registry cleaners including ccleaner then you
probably hosed your system and probably should just reinstall windows.

I havn't needed to run mine for ages, and windows at least 10 anyway
does a good job of clearing its own trash.




On 14/06/2017 7:49 a.m., Joseph Lee wrote:
> Hi,
>
> This leads me to believe that a call to Microsoft might be in order: something odd is going on with one or more NVDA components, an issue with Outlook, one or more DLL’s being unregistered or something else. Once I get confirmation from others, I’ll forward our findings to developers for further analysis.
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
> Sent: Tuesday, June 13, 2017 12:47 PM
> To: nvda@nvda.groups.io
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Yeah they do.  I had tried this as well to see if it would help but it definitely isn’t add-on related.
>
>
> Jonathan
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
> Sent: Tuesday, June 13, 2017 3:45 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi,
>
> One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
> Sent: Tuesday, June 13, 2017 12:44 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi,
>
> Hmmm, that’s concerning… Microsoft, where are you and what can we do…
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
> Sent: Tuesday, June 13, 2017 12:43 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> They have all had the same errors, this has been happening to me for ever.
>
> Sam
>
>  
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
> Sent: Tuesday, June 13, 2017 1:42 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi,
>
> Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
> Sent: Tuesday, June 13, 2017 12:39 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi Joseph,
>
>  
>
> I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors.  However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.
>
>  
>
> Jonathan
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
> Sent: Tuesday, June 13, 2017 3:37 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi,
>
> Do you know the build that was faster than before and when it came out?
>
> Cheers,
>
> Joseph
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
> Sent: Tuesday, June 13, 2017 12:23 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: Re: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi Sam,
>
>  
>
> I am having the exact same issues.  At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist.  I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs.  I don’t get it.
>
>
> Jonathan
>
>  
>
> From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>  [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Sam Bushman
> Sent: Tuesday, June 13, 2017 3:01 PM
> To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
> Subject: [nvda] NVDA Issues with Outlook 2016
>
>  
>
> Hi All,
>
>  
>
> I have tried all versions including the next and master versions and keep getting errors in outlook 2016.
>
>
> Please see my log below. Any ideas to resolve? I have done all I can.
>
>  
>
> INFO - __main__ (12:57:18.793):
>
> Starting NVDA
>
> INFO - core.main (12:57:19.717):
>
> Config dir: C:\Users\User\AppData\Roaming\nvda
>
> INFO - config.ConfigManager._loadConfig (12:57:19.717):
>
> Loading config: C:\Users\User\AppData\Roaming\nvda\nvda.ini
>
> INFO - core.main (12:57:19.980):
>
> NVDA version master-14109,35dc6213
>
> INFO - core.main (12:57:19.980):
>
> Using Windows version 10.0.15063 workstation
>
> INFO - core.main (12:57:19.980):
>
> Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]
>
> INFO - core.main (12:57:19.980):
>
> Using comtypes version 0.6.2
>
> INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):
>
> Using eSpeak NG version 1.49.1 dev
>
> INFO - synthDriverHandler.setSynth (12:57:22.025):
>
> Loaded synthDriver espeak
>
> INFO - core.main (12:57:22.025):
>
> Using wx version 3.0.2.0 msw (classic)
>
> INFO - braille.initialize (12:57:22.025):
>
> Using liblouis version 3.0.0
>
> INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):
>
> Loaded braille display driver noBraille, current display has 0 cells.
>
> INFO - brailleInput.initialize (12:57:22.039):
>
> Braille input initialized
>
> WARNING - core.main (12:57:22.078):
>
> Java Access Bridge not available
>
> INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):
>
> UIAutomation: IUIAutomation3
>
> INFO - core.main (12:57:22.536):
>
> NVDA initialized
>
> ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):
>
> __main__.main:
>
> slave error
>
> Traceback (most recent call last):
>
>    File "nvda_slave.pyw", line 90, in main
>
>    File "comHelper.pyc", line 22, in _lresultFromGetActiveObject
>
>    File "comtypes\client\__init__.pyc", line 180, in GetActiveObject
>
>    File "comtypes\__init__.pyc", line 1165, in GetActiveObject
>
>    File "_ctypes/callproc.c", line 950, in GetResult
>
> WindowsError: [Error -2147221021] Operation unavailable
>
> INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):
>
> Developer info for navigator object:
>
> name: u'Message'
>
> role: ROLE_EDITABLETEXT
>
> states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED
>
> isFocusable: True
>
> hasFocus: True
>
> Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>
>
> Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)
>
> description: None
>
> location: (11, 371, 1872, 635)
>
> value: None
>
> appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>
>
> appModule.productName: u'Microsoft Outlook'
>
> appModule.productVersion: u'16.0.8067.2157'
>
> TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>
>
> windowHandle: 67310
>
> windowClassName: u'_WwG'
>
> windowControlID: 0
>
> windowStyle: 1442840576
>
> windowThreadID: 10776
>
> windowText: u'Message'
>
> displayText: u''
>
> IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>
>
> IAccessibleChildID: 0
>
> IAccessible event parameters: windowHandle=67310, 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
>
>  
>
>  
>
>  
>
> Thank you,
>
> Sam
>
>  
>
>
>
>




Brian's Mail list account <bglists@...>
 

Actually Ccleaner does not damage systems. If you use eusing free registry cleaner you can damage things but it does have the ability to make it right again. Any registry cleaner that does not offer to back up the registry is in my opinion not worth the risk.


Of course a lot of the problems occur due to non standard use of the registry by software. This should be restored back after an uninstall but this seems not always to happen.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 10:16 PM
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Well to be honest, I had a similar issue once, if you have adobe reader dc you maybe able to temperarily fix it by doing a repair install, however every update to office in my case broke it again.

Eventually on the system with the issue I installed another version of office and it was fine though its still got some issues.

The box is quite old so eventually I will replace it.

On my other workstation I have had this issue, after my experience with microsoft, I simply just did a reformat and the problem went away.

On that note if you use registry cleaners including ccleaner then you probably hosed your system and probably should just reinstall windows.

I havn't needed to run mine for ages, and windows at least 10 anyway does a good job of clearing its own trash.




On 14/06/2017 7:49 a.m., Joseph Lee wrote:
Hi,

This leads me to believe that a call to Microsoft might be in order: something odd is going on with one or more NVDA components, an issue with Outlook, one or more DLL’s being unregistered or something else. Once I get confirmation from others, I’ll forward our findings to developers for further analysis.

Cheers,

Joseph


From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Yeah they do. I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


They have all had the same errors, this has been happening to me for ever.

Sam



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi Joseph,


I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors. However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Hi Sam,


I am having the exact same issues. At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist. I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs. I don’t get it.


Jonathan


From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA Issues with Outlook 2016


Hi All,


I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.


INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

File "nvda_slave.pyw", line 90, in main

File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

File "comtypes\__init__.pyc", line 1165, in GetActiveObject

File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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




Thank you,

Sam






Brian's Mail list account <bglists@...>
 

Cleaners should really only make a difference if you know some uninstallers cause a mess. Silverlight does this and so do some other stuff like Java.

I have never had an issue with ccleaner and keeping the registry as small as possible makes a bigger difference on standard hard drive machines than on a machine with an ssd.
Brian

bglists@blueyonder.co.uk
Sent via blueyonder.
Please address personal email to:-
briang1@blueyonder.co.uk, putting 'Brian Gaff'
in the display name field.

----- Original Message -----
From: "Gene" <gsasner@ripco.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 11:33 PM
Subject: Re: [nvda] NVDA Issues with Outlook 2016


A registry cleaner may cause damage and they usually don't improve performance. But the CCleaner registry Cleaner is considered pretty safe by the advisors I read on the subject. If a problem actually might be a registry problem, running a cleaner and not using aggressive settings might help, then again, it might not and it might cause other problems. But if you aren't having such a problem, running a cleaner introduces a certain amount of risk and no benefits.

Gene
----- Original Message -----

From: Shaun Everiss
Sent: Tuesday, June 13, 2017 4:16 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016


Well to be honest, I had a similar issue once, if you have adobe reader
dc you maybe able to temperarily fix it by doing a repair install,
however every update to office in my case broke it again.

Eventually on the system with the issue I installed another version of
office and it was fine though its still got some issues.

The box is quite old so eventually I will replace it.

On my other workstation I have had this issue, after my experience with
microsoft, I simply just did a reformat and the problem went away.

On that note if you use registry cleaners including ccleaner then you
probably hosed your system and probably should just reinstall windows.

I havn't needed to run mine for ages, and windows at least 10 anyway
does a good job of clearing its own trash.




On 14/06/2017 7:49 a.m., Joseph Lee wrote:
Hi,

This leads me to believe that a call to Microsoft might be in order: something odd is going on with one or more NVDA components, an issue with Outlook, one or more DLL’s being unregistered or something else. Once I get confirmation from others, I’ll forward our findings to developers for further analysis.

Cheers,

Joseph



From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:47 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Yeah they do. I had tried this as well to see if it would help but it definitely isn’t add-on related.


Jonathan



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:45 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi,

One more thing we can try: does the errors occur when you run NVDA with all add-ons disabled? If not, it could be an add-on.

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 12:44 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi,

Hmmm, that’s concerning… Microsoft, where are you and what can we do…

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 12:43 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



They have all had the same errors, this has been happening to me for ever.

Sam





From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 1:42 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi,

Okay, is this the case with NVDA 2016.4, 2017.1 and 2017.2? If one of those had no errors, chances are that it might be something introduced recently, but if all three have errors, then looks like a call to Microsoft might be in order.

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:39 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi Joseph,



I downloaded the nvda_snapshot_try-noGetPixel-14093,ad84027c and it seemed to help at first though with errors. However, the sluggish behavior in messages has persisted along with the error messages mostly whenever I launch and close Outlook.



Jonathan



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Joseph Lee
Sent: Tuesday, June 13, 2017 3:37 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi,

Do you know the build that was faster than before and when it came out?

Cheers,

Joseph



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io] On Behalf Of Jonathan Milam
Sent: Tuesday, June 13, 2017 12:23 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: Re: [nvda] NVDA Issues with Outlook 2016



Hi Sam,



I am having the exact same issues. At first with one of the newer Next builds, it was faster when navigating messages, but this is no longer the case, and the errors persist. I actually have to copy a message into Notepad if I want to read it if it is more than a couple of paragraphs. I don’t get it.


Jonathan



From: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> [mailto:nvda@nvda.groups.io <mailto:nvda@nvda.groups.io> ] On Behalf Of Sam Bushman
Sent: Tuesday, June 13, 2017 3:01 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA Issues with Outlook 2016



Hi All,



I have tried all versions including the next and master versions and keep getting errors in outlook 2016.


Please see my log below. Any ideas to resolve? I have done all I can.



INFO - __main__ (12:57:18.793):

Starting NVDA

INFO - core.main (12:57:19.717):

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

INFO - config.ConfigManager._loadConfig (12:57:19.717):

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

INFO - core.main (12:57:19.980):

NVDA version master-14109,35dc6213

INFO - core.main (12:57:19.980):

Using Windows version 10.0.15063 workstation

INFO - core.main (12:57:19.980):

Using Python version 2.7.13 (v2.7.13:a06454b1afa1, Dec 17 2016, 20:42:59) [MSC v.1500 32 bit (Intel)]

INFO - core.main (12:57:19.980):

Using comtypes version 0.6.2

INFO - synthDrivers.espeak.SynthDriver.__init__ (12:57:20.951):

Using eSpeak NG version 1.49.1 dev

INFO - synthDriverHandler.setSynth (12:57:22.025):

Loaded synthDriver espeak

INFO - core.main (12:57:22.025):

Using wx version 3.0.2.0 msw (classic)

INFO - braille.initialize (12:57:22.025):

Using liblouis version 3.0.0

INFO - braille.BrailleHandler.setDisplayByName (12:57:22.025):

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

INFO - brailleInput.initialize (12:57:22.039):

Braille input initialized

WARNING - core.main (12:57:22.078):

Java Access Bridge not available

INFO - _UIAHandler.UIAHandler.MTAThreadFunc (12:57:22.078):

UIAutomation: IUIAutomation3

INFO - core.main (12:57:22.536):

NVDA initialized

ERROR - RPC process 11220 (nvda_slave.exe) (12:58:15.046):

__main__.main:

slave error

Traceback (most recent call last):

File "nvda_slave.pyw", line 90, in main

File "comHelper.pyc", line 22, in _lresultFromGetActiveObject

File "comtypes\client\__init__.pyc", line 180, in GetActiveObject

File "comtypes\__init__.pyc", line 1165, in GetActiveObject

File "_ctypes/callproc.c", line 950, in GetResult

WindowsError: [Error -2147221021] Operation unavailable

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo (13:00:41.851):

Developer info for navigator object:

name: u'Message'

role: ROLE_EDITABLETEXT

states: STATE_MULTILINE, STATE_FOCUSABLE, STATE_FOCUSED

isFocusable: True

hasFocus: True

Python object: <NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject object at 0x04D11EF0>

Python class mro: (<class 'NVDAObjects.Dynamic_OutlookWordDocumentIAccessibleWordDocumentWindowNVDAObject'>, <class 'appModules.outlook.OutlookWordDocument'>, <class 'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.winword.WordDocument'>, <class 'NVDAObjects.behaviors.EditableTextWithoutAutoSelectDetection'>, <class 'editableText.EditableTextWithoutAutoSelectDetection'>, <class 'NVDAObjects.behaviors.EditableText'>, <class 'editableText.EditableText'>, <class 'NVDAObjects.window.Window'>, <class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>, <class 'baseObject.AutoPropertyObject'>, <type 'object'>)

description: None

location: (11, 371, 1872, 635)

value: None

appModule: <'outlook' (appName u'outlook', process ID 10772) at address 4c76250>

appModule.productName: u'Microsoft Outlook'

appModule.productVersion: u'16.0.8067.2157'

TextInfo: <class 'NVDAObjects.window.winword.WordDocumentTextInfo'>

windowHandle: 67310

windowClassName: u'_WwG'

windowControlID: 0

windowStyle: 1442840576

windowThreadID: 10776

windowText: u'Message'

displayText: u''

IAccessibleObject: <POINTER(IAccessible) ptr=0x62c1700 at 4df4120>

IAccessibleChildID: 0

IAccessible event parameters: windowHandle=67310, 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







Thank you,

Sam