Date   

Re: uninstalling OneCore voices

 

Well just install all the languages you want, and their voices etc etc you want.

Then you can delete the languages the same place you installed them.

And the voices should stay there and you can choose them.

On 14/06/2017 10:09 a.m., Josh Kennedy wrote:
I installed some other languages to try out their oneCore voices specifically australian english in windows10 creators edition. I no longer want the voices so I went into time region and language under settings and i removed the australian english language. I then ran the lpksetup command under cortana search and uninstalled australian english from there and restarted the computer with windows10 home 32bit. i then went into apps and features, manage optional features and it shows the australian voice features but there is only a manage button, there is no uninstall button. so how do i remove the tts and speech recognition voices and features i no longer want? do I have to reset windows10 removing all files programs and settings just to remove some voices?


Josh


Re: 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





Re: NVDA User Statistics

Brian's Mail list account
 

Is this for snaps or just the release version?
Brian

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

----- Original Message -----
From: "Joseph Lee" <joseph.lee22590@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 6:32 PM
Subject: Re: [nvda] NVDA User Statistics


Hi,
The server checks the iP addresses, hence that row. The stats are gathered when NVDA checks for updates and contacts the server in the process.
Cheers,
Joseph

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Milos Przic
Sent: Tuesday, June 13, 2017 10:30 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] NVDA User Statistics

Hi all,
Interesting stats, but there is one strange thing. There are some European Union countries listed, such as Italy, Austria, Germany etc, but then, in one point of the table, there is this stats.
European Union: Minimum 2, average 5, maximum 11. What is then counted as the European Union when all the countries belonging to it are counted separately, yet what we get here is not their sum?
Just curious.
Best!
Miloš
----- Original Message -----
From: "aikeo koomanivong" <moykoomanivong@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 07:11 PM
Subject: [nvda] NVDA User Statistics


Dear all friends.
I just want to know about NVDA statistic from around the world http://community.nvda-project.org/usersByCountry.html
how they collecting data?
Or they are using from NVDA’s server check for update .
It’s not matter but I just no for more info and teaching my students.
Thank you in advance


--
AIKEO KOOMANIVONG
CFBT-ICEVI coordinator of LAO PDR.
vise president
accessible ICT and musical development for the blind

Vocational development for LAO-blind association [VDBA] Office e-mail: vdba.lao@... Facebook page:
www.facebook.com/laoblind.org
my personal e-mail: mlp_keo@...
skype name: peba_007
mobile phone: +8562099993423
Facebook:
www.facebook.com/keo.laoblind
Linkedin:
https://www.linkedin.com/pub/aikeo-koomanivong/a7/156/b8b


Re: NVDA Issues with Outlook 2016

 

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

 


Re: Silence is golden

Brian's Mail list account
 

I have a feeling that this is not going to be possible unless somebody writes an add on for it.
Of course when you slow down speech it seems also not to lengthen pauses more than a little, but when you speed it up it seems to the ear at least that it shortens them. I do not know where the logic for this is held but it might be a question for the dev list rather than on here.

Brian

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

----- Original Message -----
From: "Giles Turnbull" <giles.turnbull@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 3:39 PM
Subject: [nvda] Silence is golden


Hi all, I wonder if anyone has any ideas on something NVDA users probably don't need to do very often. I'd like to be able to get a little bit more control over the amount of pause time that is produced by punctuation symbols.

I know a commas, semicolons and periods / full stops pause a program-controlled amount, but if I want to pause for the time of two adjacent full stops, could that be achieved in any way?

When I try the following test sentences:
This is a test sentence. It uses one full stop.
This is another test sentence. . It uses two full stops.

Sentence 1 gives me the default pause for a full stop, but sentence two produces the same amount of pause and, annoyingly, says “This is another test sentence. dot It uses two full stops.”

I was hoping I might be able to add a dictionary entry for '. .' and variants thereof, but with no success. My normal NVDA setting is for punctuation/symbol level of some, and turning it to none stops the 'dot' being announced for the second full stop, but the result is then exactly the same for both test sentences.

I won't go into more detail here about why I want to do this, but please do ask if it has any significance :)

Very grateful for any suggestions,

Giles
Abergavenny (UK)
web: http://gilesturnbullpoet.com


Re: nvda choaks up arrowing down

Brian's Mail list account
 

I think the one I posted a dropbox link to was the test version to see if the suggested cause was the cause for those experiencing the hangs and slow downs. However for it to be there for some and not others, there has to be more to it than just nvda. the fact that the test build is called nopixel or some such leads me to believe that its looking at absolute pixels and this could well take a lot longer if it has to deal with slower hardware on some machines I suppose.
Brian

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

----- Original Message -----
From: "Gene" <gsasner@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 12:42 PM
Subject: Re: [nvda] nvda choaks up arrowing down


There is no reason to believe at this time, that any of the suggestions in the message quoted below apply. Many people have reported such problems. There appears to be something in NVDA that needs fixing and it may have been fixed in the version that people tried and discussed perhaps four or five days ago. I don't remember what the term is for that version. it is a trial version to see if issues were fixed. Before worrying about processors or fans or all the other possibilities, try the trial version. Also, if another screen-reader doesn't have these problems, that, too, is evidence that the problem is an NVDA problem.

Gene
----- Original Message -----

From: Shaun Everiss
Sent: Tuesday, June 13, 2017 5:55 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] nvda choaks up arrowing down


Well I'd check startup programs.

I'd also set scheduals of security software to times when you are not
using the system or turn them off and just scan every so often.

I'd also check startup programs and use something like ccleaner to
handle those.

You could have an overheating processer or stuck fan.

In a desktop its easy enough to clear out the cpu, regrease the syncs,
replace a fan or psu and away you go.

In a laptop while at home a coolent stand under the unit and external
keyboard do help some.

For your desktop especailly if it gets hot, putting a small fan by the
case and letting it wrip is another solution, my friend who has his
computers in an atic room uses the fan to keep himself and his machines
cool, both get equally hot in there.

Failing that you could have a bad keyboard or something ran out of power.

I have had it where I will be typing on the board well wireless anyway
and suddenly the system will not respond.

There have been times where I have looked and realised I have no power
cells for the units.




On 13/06/2017 8:20 p.m., Brian's Mail list account wrote:
That sounds like the processor is getting maxed out or something has
to wait for something else to finish first.
Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Josh Kennedy"
<joshknnd1982@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 12, 2017 8:55 PM
Subject: [nvda] nvda choaks up arrowing down


about the NVDA freezing when arrowing? I opened a new ticket and
submitted a detailed debug log to the developers. the log keeps
saying debug warning trying to recover from freeze and numbers and
stuff.


--
sent with mozilla thunderbird email client







Re: NVDA Issues with Outlook 2016

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

 


Re: 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

 


Re: NVDA Issues with Outlook 2016

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

 


Re: NVDA keeps on saying unknown yet speaks in other places

Brian's Mail list account
 

Yes, but there were several others like that One was a demo of Office often supplied on a new laptop by the big warehouses that sell at cheap prices. Did I mention PC World oops sorry...

Brian

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

----- Original Message -----
From: "Gene New Zealand" <hurrikennyandopo@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 12:01 PM
Subject: Re: [nvda] NVDA keeps on saying unknown yet speaks in other places


hi brian

I reported the maths html one where when you uninstalled it it buggered up nvda, but when it was re installed it fixed it up and nvda worked again.

Gene nz

On 13/06/2017 8:08 PM, Brian's Mail list account wrote:
There used to be a Microsoft fixit for this in xp and 7. seems odd if its in 10. Would be interesting to know if the machine was always used with a screenreader and originally was 7.
Also I seem to recall a lot of this is often due to a particular file not being registered. I last saw this from Jamie on the dev list perhaps a year or so ago? anyone remember what file it was? Again it was due to an uninstall of some program.
Brian

bglists@...<mailto:bglists@...>
Sent via blueyonder.
Please address personal email to:-
briang1@...<mailto:briang1@...>, putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Gene" <gsasner@...><mailto:gsasner@...>
To: <nvda@nvda.groups.io><mailto:nvda@nvda.groups.io>
Sent: Monday, June 12, 2017 10:12 AM
Subject: Re: [nvda] NVDA keeps on saying unknown yet speaks in other places


Ask if someone removed Word or Office. It sounds as though someone did something like that which damages Windows ability to work with NVDA. I don't know if the problem can be corrected other than by doing something like reverting Windows using the Windows 10 feature. But I don't know if everything must be removed or if Windows can be reverted while keeping installed programs. Others who know more will, I hope comment.

Gene


From: Gene New Zealand
Sent: Monday, June 12, 2017 3:30 AM
To: nvda@nvda.groups.io<mailto:nvda@nvda.groups.io>
Subject: [nvda] NVDA keeps on saying unknown yet speaks in other places


hi guys




i have a lady who gave me her laptop. She is running Windows 10 with the anniversary version of windows. it is a 64 bit machine and has NVDA 2017.2 on it at present.

she has mozilla thunder bird and fire fox etc on it.

there are no viruses etc on it.




NVDA starts up and is using the e speak synth.




some of the things it is doing like when you tab say from the start menu across the taskbar where the running applications are it is saying unknown. Ausing the arrow keys nvda will not speak any thing. A sighted person said there is little icons there but are not getting read out. it will speak the windows notification area and also the desktop. You can arrow around etc and that part works. You can go into NVDAs menus etc. You can also go into windows explorer and navigate there as well. But the menus up the topwill only speak the main tabs and not any thing as you tab down the list.




When you go into mozilla thunder bird it just says unknown as you tab. you can not even get into the menus up the top with the alt key etc.




the same sort of thing happens in mozilla fire fox and there is a page loaded which it does not speak. it will not even speak the menus up the top either. Quick navigation keys do not even work.

I have even uninstalled NVDA totally both through the program and features section and also under the %appdata% section then installed a clean copy of NVDA, yet the same results.




At present i am doing a system restore to a earlier date but will not know until it boots up if the problems is still there.




The applications key when pressed i got told it comes up, but nvda does not speak it when you arrow down the menu.




any ideas i could try? I have also tried it from a thumb drive with a good working copy, but still the same results.

I will try and get a nvda log and send it so you guys might get a better idea of what is happening.




Gene nz








--
[Image NVDA certified expert]
Check out my website for NVDA tutorials and other blindness related material at http://www.accessibilitycentral.net Regardless of where you are in New Zealand if you are near one of the APNK sites you can use a copy of the NVDA screen reader on one of their computers. To find out which locations (or location) is near to you please visit http://www.aotearoapeoplesnetwork.org/content/partner-libraries (Aotearoa People's Network Kaharoa). To find an NVDA certified expert near you, please visit the following link https://certification.nvaccess.org/. The certification page contains the official list of NVDA certified individuals from around the world, who have sat and successfully passed the NVDA expert exam.


Re: NVDA Issues with Outlook 2016

 

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

 


Re: Test please do not reply

Brian's Mail list account
 

Only have access to spam on imap or web mail but if it was delivered to spam it technically would not be seen as a bounce to io would it in any case.
No I suspect black listing going on.
Brian

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

----- Original Message -----
From: "Shaun Everiss" <sm.everiss@...>
To: <nvda@nvda.groups.io>
Sent: Tuesday, June 13, 2017 11:39 AM
Subject: Re: [nvda] Test please do not reply


Hmmm.

well checking spam maybe, contacting your isp could help.

The only time I have had this happen was before ssl came along and it was an optional feature not standard.

Anyway I was on yahoogroups and needed ssl for remote mail.

Yahoogroups did not support ssl they do now like everything else.

Anyway I was bouncing and getting banned and all sorts of junk.

I contacted the support people and told them I was on an ssl connection, and they manually got me out of the bounce issue.

If things keep bouncing I strongly suggest you ditch your isps email and just use gmail.

I had to do this when I switched isps and this has helped me a lot as a lot of services require jumping through hoops to update contact info.

Today for example I was updating my soon to be expired government taxi transport card, and was assured that I could do it online.

However after getting a sightling to read the details to me from the paper form, my email address was not correct.

I then had to sign for the form, and then I couldn't pay online only by check only and I don't write those.

Luckily my dad helped me, wrote one and sent the check today and form else no transport card for me unless I took a trip into town to the local blindy organisation, to get another appointment to fill out another form which while it wouldn't cost me more cash would mean more wasted time.

It can take around 20 minutes to an hour to get into town on the roads or a little less with busses.

Point is, I'd have to travel 2 hours and wait 20 minutes for an appointment, pay 8 bucks and fill out a 5 minute form.

And while for security reasons from time to time I do actually do this, I would prefur not to.

Imagine if I had to do this for every fuzzing email address change.

I could actually say stronger words and while I know that this is probably an isolated case with the tech we have its still worth noting down.

There are ofcause disadvantages to getting off isp mail, the main ones are lack of local support and well at least in basic mode on gmail I can't empty my trash folder as such.

On the otherside, I don't need to worry about antivirus protection or fishing, or any security at all for my email thats handled by google.

I don't have to bother about anyone hacking my account google has a good track record I have even managed to trip the defence turrits from time to time and its not nice to get hit.

The spam system is usually good, and if you allow enough non spam stuff out of spam the system will learn from you.

I also have full ssl and can access the stuff I want world wide.

I also have 15 gb of space for everything from email to files, to other services including a calendar which on win10 really does rock.




On 13/06/2017 7:54 p.m., Brian's Mail list account wrote:
In addition to other lists asking me to confirm, groups.io now has saying the emails to me are bouncing. This cannot be true as I can see current emails, so I've clicked the unbounce and am just testing this group.
Brian

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




Re: NVDA Issues with Outlook 2016

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

 


Re: NVDA Issues with Outlook 2016

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

 


Re: 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

 


Re: 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

 


Re: NVDA Issues with Outlook 2016

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

 


Re: 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

 


Re: NVDA Issues with Outlook 2016

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

 


Re: 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

 

82721 - 82740 of 102727