Date   

Re: Introducing Virtual Review 2.1 #addonrelease

Sam Bushman
 

A Universal Windows app is a software application written in the Windows 8 or Windows 10 codebase that can run not just on a Windows PC, but also on a Windows tablet, smartphone, smartwatch or XBox as well.

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Andre Fisher
Sent: Monday, June 19, 2017 6:26 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Introducing Virtual Review 2.1 #AddonRelease

Google it

On 6/19/17, Sam Bushman <libertyroundtable@gmail.com> wrote:
What is a universal app?





From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of
David Moore
Sent: Monday, June 19, 2017 5:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Introducing Virtual Review 2.1 #AddonRelease



Hi Joseph and all!

This add on is very exciting for universal apps. I am using this add
on to use the Facebook and Twitter apps much better. Also, this add on
is helping me use Groove app much better. There is a lot of future in
this add on. I will post all of my findings of what I can do with this
add on that I could not do before!

David Moore

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for
Windows
10



From: Joseph Lee <mailto:joseph.lee22590@gmail.com>
Sent: Monday, June 19, 2017 1:38 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] Introducing Virtual Review 2.1 #AddonRelease



Dear NVDA community:



Virtual Review 2.1 is ready for download. This add-on lets you review
screen content on a browse mode window when you press Control+NVDA+W.



Virtual Review 2.1 is specifically designed for Windows 8.x and 10
users, mostly benefits Windows 10 users. In particular, you can now
(are you ready for this?) review screen contents of universal apps via
virtual review window. This version also lets you see the title of the
window you are virtually reviewing.



The add-on page is at:

<https://addons.nvda-project.org/addons/virtualRevision.en.html>
https://addons.nvda-project.org/addons/virtualRevision.en.html



Cheers,

Joseph






Re: NVDA and IE11 problems

Gene New Zealand <hurrikennyandopo@...>
 

Hi


you could always try the following.


when you are in internet exploder and you are focused in it try the nvda key + letter V.

it should say if screen layout is either on or off. I usually have mine to off, this is a toggle and is spoken.
This also puts text and links on the same line.

the second question use the nvda key + space bar, it should toggle it between browse mode where you can use single letter navigation keys and focus mode where you can type.

Best bet  is to find the edit areas is to use the letter E and this should take you from where ever you are to a edit area. I usually do this from the top of a page. the other letter I use at times is the letter F and when i land on those areas if i do not hear it spoken as in focus mode i then use the nvda key + space bar to do it.

If you want to hear NVDA say browse mode and focus mode take a look under the browse mode setting in nvda and uncheck the box that says Audio indication of focus and browse modes then tab to the ok button then give it a whirl in the browser. if happy with how it plays then you can save your configuration.

Gene nz
 

On 6/20/2017 1:37 PM, Don H wrote:
Running latest released version of NVDA on a Win 10 64 bit machine. When I use IE 11 often times I have two issues.  First is not being able to open a link.  When on a link I hit enter and get nothing.
Second I will move to a edit box and can not get NVDA in the right mode to enter text.  Tried resetting IE and did not help.  Seems to happen on a random basis on random pages.
Any help would be appreciated.
 en




--
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 and IE11 problems

Gene New Zealand <hurrikennyandopo@...>
 

Hi


you could always try the following.


when you are in internet exploder and you are focused in it try the nvda key + letter V.

it should say if screen layout is either on or off. I usually have mine to off, this is a toggle and is spoken.
This also puts text and links on the same line.

the second question use the nvda key + space bar, it should toggle it between browse mode where you can use single letter navigation keys and focus mode where you can type.

Best bet  is to find the edit areas is to use the letter E and this should take you from where ever you are to a edit area. I usually do this from the top of a page. the other letter I use at times is the letter F and when i land on those areas if i do not hear it spoken as in focus mode i then use the nvda key + space bar to do it.

If you want to hear NVDA say browse mode and focus mode take a look under the browse mode setting in nvda and uncheck the box that says Audio indication of focus and browse modes then tab to the ok button then give it a whirl in the browser. if happy with how it plays then you can save your configuration.

Gene nz
 

On 6/20/2017 1:37 PM, Don H wrote:
Running latest released version of NVDA on a Win 10 64 bit machine. When I use IE 11 often times I have two issues.  First is not being able to open a link.  When on a link I hit enter and get nothing.
Second I will move to a edit box and can not get NVDA in the right mode to enter text.  Tried resetting IE and did not help.  Seems to happen on a random basis on random pages.
Any help would be appreciated.
 en




--
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: Important directive for Windows 10 users: there is a reason why Windows 10 App Essentials add-on is out there...

Brandon Cross <bcross3286@...>
 

Here's the problem, an addon is just that, something you bolt on, or tack on to a piece of software to extend it, or give it some added functionality. Just because you have developed addons, does not give you the right to issue directives on high to anyone, for any reason. This is egotistical and arrogant, and while I'm sure you have good intentions at heart, my blood boiled when I saw that. We are all not like you, we all don't run the latest insider fast ring builds. Some of us only have one machine, either that, or we just prefer to use something that's going to be more stable. I personally have made the choice to stay clear of insider builds after several bad experiences with them across two separate machines. You probably have a core of testers who will do what you want them to do, or need them to do, the rest of us are just end-users, and are not subject to your whims, no matter how much they may help you in the future. I honestly wonder if anyone else didn't blow up at those words. I don't usually like to partake in back and forth drama, but this just takes the cake as far as I'm concerned. You're an addon dev and work with the NVDA team, this does not make you god. You need to learn that right off. I personally use a few of your addons and enjoy them, and appreciate the work you put into them, however, as I mentioned above, the narcissism needs to stop from you.


NVDA and IE11 problems

Don H
 

Running latest released version of NVDA on a Win 10 64 bit machine. When I use IE 11 often times I have two issues. First is not being able to open a link. When on a link I hit enter and get nothing.
Second I will move to a edit box and can not get NVDA in the right mode to enter text. Tried resetting IE and did not help. Seems to happen on a random basis on random pages.
Any help would be appreciated.
en


Re: dictation bridge?

 

can I get a link to the latest beta afain?

tthanks Hank

On 6/19/2017 5:40 PM, Pranav Lal wrote:

Hi Ken,

 

DictationBridge will be out soon. There are a few things we are fixing. Have you tried the beta?

 

Pranav



Re: NVDA Issues with Outlook 2016

Pranav Lal
 

Hi Sam,

 

I use Outlook 2016 regularly at home and have not had these issues.

 

Are you on the latest version of windows 10? I do not think so. Can you upgrade?

Pranav


Re: NVDA Issues with Outlook 2016

Pranav Lal
 

Hi Sam,

 

I am coming late to this discussion but do the errors occur when you run outlook in safe mode?

 

Pranav

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Sam Bushman
Sent: Wednesday, June 14, 2017 1:13 AM
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: dictation bridge?

Pranav Lal
 

Hi Ken,

 

DictationBridge will be out soon. There are a few things we are fixing. Have you tried the beta?

 

Pranav


Re: Introducing Virtual Review 2.1 #addonrelease

Andre Fisher
 

Google it

On 6/19/17, Sam Bushman <libertyroundtable@gmail.com> wrote:
What is a universal app?





From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of David
Moore
Sent: Monday, June 19, 2017 5:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Introducing Virtual Review 2.1 #AddonRelease



Hi Joseph and all!

This add on is very exciting for universal apps. I am using this add on to
use the Facebook and Twitter apps much better. Also, this add on is helping
me use Groove app much better. There is a lot of future in this add on. I
will post all of my findings of what I can do with this add on that I could
not do before!

David Moore

Sent from Mail <https://go.microsoft.com/fwlink/?LinkId=550986> for Windows
10



From: Joseph Lee <mailto:joseph.lee22590@gmail.com>
Sent: Monday, June 19, 2017 1:38 PM
To: nvda@nvda.groups.io <mailto:nvda@nvda.groups.io>
Subject: [nvda] Introducing Virtual Review 2.1 #AddonRelease



Dear NVDA community:



Virtual Review 2.1 is ready for download. This add-on lets you review screen
content on a browse mode window when you press Control+NVDA+W.



Virtual Review 2.1 is specifically designed for Windows 8.x and 10 users,
mostly benefits Windows 10 users. In particular, you can now (are you ready
for this?) review screen contents of universal apps via virtual review
window. This version also lets you see the title of the window you are
virtually reviewing.



The add-on page is at:

<https://addons.nvda-project.org/addons/virtualRevision.en.html>
https://addons.nvda-project.org/addons/virtualRevision.en.html



Cheers,

Joseph






Re: A question about non destructive errors

Sam Bushman
 

If someone could please add this issue – it gets the error when you launch outlook. Joseph is caught up on this issue as well.

Thanks,

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:48 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A question about non destructive errors

 

We've got a few issues for Outlook: https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20outlook%202016

 

I'll have a look through and see if I can find anything similar, but feel free to also look and / or add a new issue in the meantime.

 

Regards

 

Quentin.

 

On Tue, Jun 20, 2017 at 9:30 AM, Sam Bushman <libertyroundtable@...> wrote:

I am in ms office outlook 2016.

I get a two tone error when this happens.

Can’t ready the emails either.

Thanks,

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:28 PM


To: nvda@nvda.groups.io
Subject: Re: [nvda] A question about non destructive errors

 

What were you doing when you pressed down arrow (It looks like pressing down arrow has triggered it)?

 

On Tue, Jun 20, 2017 at 9:25 AM, Sam Bushman <libertyroundtable@...> wrote:

I get the following errors:

 

ERROR - scriptHandler.executeScript (13:30:32.572):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x04EA1270>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - RPC process 4468 (nvda_slave.exe) (13:44:26.766):

__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

ERROR - scriptHandler.executeScript (13:45:32.332):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0507CF50>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - scriptHandler.executeScript (14:02:51.563):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0513E7F0>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

 

 

Any Way I can help resolve?

 

Thanks,

Sam

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:21 PM
To: nvda@nvda.groups.io


Subject: Re: [nvda] A question about non destructive errors

 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

 

Regards


Quentin.

 

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:

Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors

 

Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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



--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

 

 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Introducing Virtual Review 2.1 #addonrelease

Sam Bushman
 

What is a universal app?

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of David Moore
Sent: Monday, June 19, 2017 5:59 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Introducing Virtual Review 2.1 #AddonRelease

 

Hi Joseph and all!

This add on is very exciting for universal apps. I am using this add on to use the Facebook and Twitter apps much better. Also, this add on is helping me use Groove app much better. There is a lot of future in this add on. I will post all of my findings of what I can do with this add on that I could not do before!

David Moore

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Monday, June 19, 2017 1:38 PM
To: nvda@nvda.groups.io
Subject: [nvda] Introducing Virtual Review 2.1 #AddonRelease

 

Dear NVDA community:

 

Virtual Review 2.1 is ready for download. This add-on lets you review screen content on a browse mode window when you press Control+NVDA+W.

 

Virtual Review 2.1 is specifically designed for Windows 8.x and 10 users, mostly benefits Windows 10 users. In particular, you can now (are you ready for this?) review screen contents of universal apps via virtual review window. This version also lets you see the title of the window you are virtually reviewing.

 

The add-on page is at:

https://addons.nvda-project.org/addons/virtualRevision.en.html

 

Cheers,

Joseph

 


Re: Introducing Virtual Review 2.1 #addonrelease

David Moore
 

Hi Joseph and all!

This add on is very exciting for universal apps. I am using this add on to use the Facebook and Twitter apps much better. Also, this add on is helping me use Groove app much better. There is a lot of future in this add on. I will post all of my findings of what I can do with this add on that I could not do before!

David Moore

Sent from Mail for Windows 10

 

From: Joseph Lee
Sent: Monday, June 19, 2017 1:38 PM
To: nvda@nvda.groups.io
Subject: [nvda] Introducing Virtual Review 2.1 #AddonRelease

 

Dear NVDA community:

 

Virtual Review 2.1 is ready for download. This add-on lets you review screen content on a browse mode window when you press Control+NVDA+W.

 

Virtual Review 2.1 is specifically designed for Windows 8.x and 10 users, mostly benefits Windows 10 users. In particular, you can now (are you ready for this?) review screen contents of universal apps via virtual review window. This version also lets you see the title of the window you are virtually reviewing.

 

The add-on page is at:

https://addons.nvda-project.org/addons/virtualRevision.en.html

 

Cheers,

Joseph

 


Re: A question about non destructive errors

Quentin Christensen
 

We've got a few issues for Outlook: https://github.com/nvaccess/nvda/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20outlook%202016

I'll have a look through and see if I can find anything similar, but feel free to also look and / or add a new issue in the meantime.

Regards

Quentin.

On Tue, Jun 20, 2017 at 9:30 AM, Sam Bushman <libertyroundtable@...> wrote:

I am in ms office outlook 2016.

I get a two tone error when this happens.

Can’t ready the emails either.

Thanks,

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:28 PM


To: nvda@nvda.groups.io
Subject: Re: [nvda] A question about non destructive errors

 

What were you doing when you pressed down arrow (It looks like pressing down arrow has triggered it)?

 

On Tue, Jun 20, 2017 at 9:25 AM, Sam Bushman <libertyroundtable@...> wrote:

I get the following errors:

 

ERROR - scriptHandler.executeScript (13:30:32.572):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x04EA1270>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - RPC process 4468 (nvda_slave.exe) (13:44:26.766):

__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

ERROR - scriptHandler.executeScript (13:45:32.332):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0507CF50>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - scriptHandler.executeScript (14:02:51.563):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0513E7F0>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

 

 

Any Way I can help resolve?

 

Thanks,

Sam

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:21 PM
To: nvda@nvda.groups.io


Subject: Re: [nvda] A question about non destructive errors

 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

 

Regards


Quentin.

 

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:

Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors

 

Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

 

 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: A question about non destructive errors

Sam Bushman
 

I am in ms office outlook 2016.

I get a two tone error when this happens.

Can’t ready the emails either.

Thanks,

Sam

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:28 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A question about non destructive errors

 

What were you doing when you pressed down arrow (It looks like pressing down arrow has triggered it)?

 

On Tue, Jun 20, 2017 at 9:25 AM, Sam Bushman <libertyroundtable@...> wrote:

I get the following errors:

 

ERROR - scriptHandler.executeScript (13:30:32.572):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x04EA1270>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - RPC process 4468 (nvda_slave.exe) (13:44:26.766):

__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

ERROR - scriptHandler.executeScript (13:45:32.332):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0507CF50>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - scriptHandler.executeScript (14:02:51.563):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0513E7F0>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

 

 

Any Way I can help resolve?

 

Thanks,

Sam

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:21 PM
To: nvda@nvda.groups.io


Subject: Re: [nvda] A question about non destructive errors

 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

 

Regards


Quentin.

 

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:

Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors

 

Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

 

 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: A question about non destructive errors

Quentin Christensen
 

What were you doing when you pressed down arrow (It looks like pressing down arrow has triggered it)?

On Tue, Jun 20, 2017 at 9:25 AM, Sam Bushman <libertyroundtable@...> wrote:

I get the following errors:

 

ERROR - scriptHandler.executeScript (13:30:32.572):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x04EA1270>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - RPC process 4468 (nvda_slave.exe) (13:44:26.766):

__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

ERROR - scriptHandler.executeScript (13:45:32.332):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0507CF50>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - scriptHandler.executeScript (14:02:51.563):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0513E7F0>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

 

 

Any Way I can help resolve?

 

Thanks,

Sam

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:21 PM
To: nvda@nvda.groups.io


Subject: Re: [nvda] A question about non destructive errors

 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

 

Regards


Quentin.

 

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:

Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors



Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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





--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

 

 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 




--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: A question about non destructive errors

Sam Bushman
 

I get the following errors:

 

ERROR - scriptHandler.executeScript (13:30:32.572):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x04EA1270>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - RPC process 4468 (nvda_slave.exe) (13:44:26.766):

__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

ERROR - scriptHandler.executeScript (13:45:32.332):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0507CF50>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

COMError: (-2147352319, None, (None, None, None, 0, None))

ERROR - scriptHandler.executeScript (14:02:51.563):

error executing script: <bound method MSHTML.script_moveByLine_forward of <virtualBuffers.MSHTML.MSHTML object at 0x0513E7F0>> with gesture u'down arrow'

Traceback (most recent call last):

  File "scriptHandler.pyc", line 187, in executeScript

  File "cursorManager.pyc", line 209, in script_moveByLine_forward

  File "cursorManager.pyc", line 139, in _caretMovementScriptHelper

  File "browseMode.pyc", line 1150, in _set_selection

  File "browseMode.pyc", line 1165, in _shouldSetFocusToObj

  File "baseObject.pyc", line 34, in __get__

  File "baseObject.pyc", line 110, in _getPropertyViaCache

  File "NVDAObjects\IAccessible\MSHTML.pyc", line 925, in _get_isFocusable

  File "comtypes\client\lazybind.pyc", line 207, in __call__

  File "comtypes\automation.pyc", line 664, in _invoke

 

 

Any Way I can help resolve?

 

Thanks,

Sam

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Quentin Christensen
Sent: Monday, June 19, 2017 5:21 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] A question about non destructive errors

 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

 

Regards


Quentin.

 

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:

Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors



Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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





--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess

 

 



 

--

Quentin Christensen
Training and Support Manager

 

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

 

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: A question about non destructive errors

Quentin Christensen
 

Oh it's definitely worth raising any situations that cause an error.  Errors which also have a negative effect for the end-user will be given a higher priority to fix obviously, especially since error tones aren't generated for the stable releases.

Regards

Quentin.

On Mon, Jun 19, 2017 at 5:17 PM, Brian's Mail list account <bglists@...> wrote:
Hmm, I'm sure they know about this error condition, but I'm always a little sceptical  when I see errors that in the end it might be a problem that could cause issues if you don't trap it somehow.



Brian

bglists@...
Sent via blueyonder.
Please address personal email to:-
briang1@..., putting 'Brian Gaff'
in the display name field.
----- Original Message ----- From: "Quentin Christensen" <quentin@...>
To: <nvda@nvda.groups.io>
Sent: Monday, June 19, 2017 12:31 AM
Subject: Re: [nvda] A question about non destructive errors



Hi Brian,

Without being specifically familiar with this particular code, a couple of
points off the top of my head:

- Often different programs (and sometimes even the same program) will have
controls which may look and behaves exactly the same to the end user, but
underneath they work differently.  This can be why some controls throw up
errors when others do not.
- Partly for the same reason, if we try and find out information a certain
way and it fails, there may be another (backup, if you like) way that we
can try which may get the same information.  In that case, the control may
throw up an error, but appear to work as normal.
- My lack of familiarity with the code will show here, but the error about
CoInitialize not being called is likely because it would be usual to
initialize that prior to making a certain request.  For whatever reason
that wasn't done, which may in some situations mean that the value returned
by that request may be unexpected.  Whether that's a problem or not I'd
need Mick or Jamie to answer, but all that might give you a bit of an idea
to start with.  Again, that's all just general off the top of my head and
without being specifically familiar with the code.

Regards

Quentin.

On Sun, Jun 18, 2017 at 11:28 PM, Brian's Mail list account <
bglists@...> wrote:

As quite a lot of us do use snapshot builds we do hear errors from time to
time. one of the most annoying ones I see in windows 7 is when some of the
search fields are used. There can be multiple errors as one types in and
even when the edit area is opened, yet to all  intents and purposes it
seems like the control itself has worked.
Here is a log to demonstrate what I mean.

IO - inputCore.InputManager.executeGesture (14:18:51.645):
Input: kb(desktop):shift+tab
IO - speech.speak (14:18:51.730):
Speaking [LangChangeCommand ('en_GB'), u'Search Box  edit   Search Windows
(C:)']
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.732):
_getTextWithFieldsForUIARange
DEBUG - NVDAObjects.UIA.UIATextInfo._getTextWithFieldsForUIARange
(14:18:51.733):
rootElement: edit
ERROR - eventHandler.executeEvent (14:18:51.733):
error executing event: gainFocus on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\easyTableNavigat
or\globalPlugins\easyTableNavigator.py", line 82, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\
globalPlugins\focusHighlight.py", line 427, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "appModules\explorer.pyc", line 280, in event_gainFocus
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 907, in event_gainFocus
 File "NVDAObjects\__init__.pyc", line 819, in reportFocus
 File "speech.pyc", line 367, in speakObject
 File "speech.pyc", line 689, in speakTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 584, in getTextWithFields
 File "NVDAObjects\UIA\__init__.pyc", line 444, in
_getTextWithFieldsForUIARange
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.740):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))
ERROR - eventHandler.executeEvent (14:18:51.752):
error executing event: caret on <NVDAObjects.Dynamic_EditableT
extWithoutAutoSelectDetectionUIA object at 0x05C24D90> with extra args of
{}
Traceback (most recent call last):
 File "eventHandler.pyc", line 143, in executeEvent
 File "eventHandler.pyc", line 91, in __init__
 File "eventHandler.pyc", line 98, in next
 File "NVDAObjects\__init__.pyc", line 940, in event_caret
 File "review.pyc", line 167, in handleCaretMove
 File "NVDAObjects\__init__.pyc", line 973, in makeTextInfo
 File "NVDAObjects\UIA\__init__.pyc", line 244, in __init__
COMError: (-2147221008, 'CoInitialize has not been called.', (None, None,
None, 0, None))


This is in the master branch and has been around for quite some time now
but of course one does not hear it on the final builds.
Also quit why it refers to two add-ons which would seem to have nothing to
do with it is a mystery as well.
Just wondered why this c_inisialise or whatever is not called and why it
seems that some edit areas work while others do not.

Brian

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






--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available:
http://www.nvaccess.org/shop/

Ph +61 7 3149 3306
www.nvaccess.org
Facebook: http://www.facebook.com/NVAccess
Twitter: @NVAccess








--
Quentin Christensen
Training and Support Manager

Basic Training for NVDA & Microsoft Word with NVDA E-Books now available: http://www.nvaccess.org/shop/

www.nvaccess.org 
Facebook: http://www.facebook.com/NVAccess 
Twitter: @NVAccess 


Re: Important directive for Windows 10 users: there is a reason why Windows 10 App Essentials add-on is out there...

Robin Frost
 

Hi,
Perhaps I’m fool hearty to even try but in the interest of clarity I’ll attempt to address Gene’s assessment of my post as that’s what I believe is being referenced below.
Firstly I am by no means a fan girl type of person of any particular operating system, screen reader or device. I’ll use that which does any task the best at any given time. That is why I made reference to the fact that others often can and do pick devices operating systems and all manner of things based on any number of reasons I just didn’t want to think that people might do so out of fear based upon things that might not afflict them. I also indicated that my experience was different that others as I did not upgrade but rather was forced by circumstances to purchase a new machine thus my Windows 10 install was a clean one from a manufacturer.
I acknowledge that Windows is by no means perfect but I don’t expect it to be so as nothing is. I do however, agree that users just want a machine that works and does that which they need it to do daily; and I also agree that in an optimal world an operating system manufacturer should make sure that it works with as many screen readers and other variables as possible and I agree that saying it works well with Narrator doesn’t qualify as such.
However, it is also my understanding that to at least some degree screen reader manufacturers often do dialog with Microsoft behind the scenes and participate in running insider builds in an effort to address accessibility issues before they role out. if I am incorrect on this point I’m sure someone will further enlighten us all.
 
And for the record I have experienced Microsoft updates causing issues with drivers and peripherals from time to time but when I did it was nothing that couldn’t be solved by either a call to Microsoft’s disability help desk or my pc’s own manufacturer as recently as the last 2 weeks.
 
Again in summation I would never presume to make any sort of grand pronouncement on that which anyone would or should do I was merely trying to balance that which had been stated with another view. And with that I’ll now post this with the fragile fleeting hope that this might clarify that which I had tried to say and perhaps did so unsuccessfully.
Robin
 
 

From: Gene
Sent: Monday, June 19, 2017 4:07 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important directive for Windows 10 users: there is a reason why Windows 10 App Essentials add-on is out there...
 
I evidently respondedd to a message that didn't include the comments I was responding to.  As far as I know, it was in this thread that someone said that their Windows 10 has worked well and that they object to the characterizations of some users that it doesn't in general.  I'm not completely paraphrasing the message correctly, I evidently no longer have it but that gives readers following the thread enough information to know what message I was commenting on.
 
Gene
----- Original Message -----
From: Gene
Sent: Monday, June 19, 2017 2:30 PM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important directive for Windows 10 users: there is a reason why Windows 10 App Essentials add-on is out there...
 
This message is long; you may want to read it now or when you have more time, if you are busy now.
 
You have stated how you found Windows on one machine.  It isn't a fact in general.  it is a fact regarding your personal experience.  It is my impression that a lot of people have found Windows 10 to be reliable.  But, in the case of blind users, many continually have problems with Microsoft making changes to universal apps that degrades accessibility in those apps.  Do you use universal apps such as the mail app or do you use Windows 10 to run traditional programs? 
 
Just yesterday, on the NVDA users list, there was discussion of how the e-mail app had serious problems after Microsoft updated it in terms of accessibility.  the problems could be corrected by using the latest version of the add on for NVDA that is released by NVDA, largely to deal with the unending problems Microsoft causes by not testing its apps properly for accessibility.  I believe it was on this list yesterday or the day before that I asked about Microsoft testing its universal apps.  An NVDA developer said that Microsoft tests them using Narrator.  That's not anything remotely resembling proper testing. 
 
My point is that your experience is very conditional.  If you had driver problems and forced driver updates kept undoing the changes you made to cause your system to work properly, you wouldn't have as good an experience as you report.  If you used universal apps, your experience would be a cat and mouse game depending on how well and how quickly your screen-reader delt with the changes Microsoft made to these apps after releasing them with completely inadequate testing.  And there is a basic principle that a machine owner has the right to control what is done to his/her machine.  Microsoft, in not allowing updates to be controled as in previous versions of Windows is, in effect, asserting the right to control your, not their, machine.  They license Windows to you, they don't license your machine to you.
 
Microsoft gave Windows 10 away for free to meet their financial goals to monitize Windows, not the users best interests.  I am very glad that I didn't fall for Microsoft's snake oil.  My Windows 7 machine works well and I can do everything I want to with it.  I control my machine, not Microsoft.  I will not upgrade my well working, reliable Windows 7 machine to Windows 10.  When I buy a new computer, it will have Windows 10 on it.  I won't upgrade to Windows 10 just because Microsoft does everything it can to entice me to do so for their advantage, not mine. 
 
Gene
----- Original Message -----
Monday, June 19, 2017 9:55 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important directive for Windows 10 users: there is a
reason why Windows 10 App Essentials add-on is out there...

I echo the same sentiment as Brian.  The Win10 anniversary already caused me
to buy another laptop I did not need as I was leaving on an overseas trip
and my laptop was totally messed up after the update.  I am honestly about
to switch to a Mac as the Win environment is not reliable.
Blessings
Pascal

-----Original Message-----
From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Austin
Pinto
Sent: Monday, June 19, 2017 4:02 AM
To: nvda@nvda.groups.io
Subject: Re: [nvda] Important directive for Windows 10 users: there is a
reason why Windows 10 App Essentials add-on is out there...

oh! when you said explode i thought it would sound much worced but.
its a nice directive

On 6/19/17, Brian's Mail list account <bglists@...> wrote:
> Joseph, though I do understand where you are coming from and the
> frustration
>
> you feel, I do honestly have sympathy with the end user who just wants
> a reliable system.
> Microsoft have to shoulder a good deal of the blame for what their
> changes cause. I'm not suggesting in any way that they are
> deliberately  screwing things up here, just that they  really do not
> test stuff enough. For people
>
> who do not use special builds of windows, ie insiders, or nvda. I do
> not think it unreasonable to expect continuity and after a while
> people do get fed up with having the rug pulled from under them on a
> regular basis by software makers, be that Microsoft or anyone else.
>  So yes, in a development environment you would be justified in being
> annoyed, but when people are trying to run their lives day to day and
> keep encountering stones in the road and potholes not of their own
> making  it is,
>
> I think understandable if people get fed up and take the easy option.
>  I have I know said much of this before, but like most of us, I have
> had to
>
> try to help people in real life away from this place and been almost
> embarrassed when you eventually track down the issue to the actual
> changes in the software and nothing to do with the end user, except
> that he or she happens to be blind.
>
> I'll shut up now and  be quiet, bite my lip etc for a while. I nearly
> bought
>
> a new laptop last week but after reading about all the win 10 issues
> decided
>
> not to bother.
>  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: Monday, June 19, 2017 4:22 AM
> Subject: [nvda] Important directive for Windows 10 users: there is a
> reason
>
> why Windows 10 App Essentials add-on is out there...
>
>
>> Dear NVDA community,
>>
>>
>>
>> Disclaimer: for new community members, I'm normally not like this,
>> but I do sometimes right posts I believe folks should hear, as it
>> impacts community experience and what not. So my sincere apologies
>> for letting you witness my explosive side. Please bear with me for a
>> second, as it is important that
>>
>> I
>> talk about the following regarding respecting engineers and announce
>> a directive for Windows 10 users:
>>
>>
>>
>> In the blindness community (at least for members of various mailing
>> lists that I'm a part of or lead), I became synonymous with someone
>> who is willing to show patience until the end, especially when
>> resolving tech support problems. But there is a hidden side to that:
>> for certain things, I become
>>
>> a
>> volcano, and those who've witnessed my lava flow knows what I mean.
>> Unfortunately, I believe it is time that I explode yet again (my
>> apologies to our dear leaders for doing something like this):
>>
>>
>>
>> Answering questions: for many situations, when resolving issues, when
>> I and other engineers ask you questions in hopes of getting to the
>> meat of the burger. Sometimes we may ask you to tell us steps to
>> reproduce the given problem, what a screen reader says, and what not.
>> When developers ask you questions, please do your best to answer them
>> if possible.
>>
>>
>>
>> For Windows 10 users: there is an important reason why I wrote
>> Windows 10 App Essentials: to prevent issues like the one Rosemarie
>> and others have experienced with Mail app. Hence the following directive:
>>
>>
>>
>> Until now, it was optional for you to use Windows 10 app Essentials
>> add-on if you are using Windows 10. I'll make this an important
>> requirement starting from fall 2017. That is, starting from September
>> 2017, when you report issues like the one Rosemarie has experienced,
>> I'll no longer ask you to install latest WinTenApps add-on: I'll
>> assume that you have. For Windows Insiders, this is a critical (and
>> mandatory) requirement.
>>
>>
>>
>> I'm not announcing this directive just because I feel like doing it,
>> nor to increase popularity of my brainchild: Windows 10 App
>> Essentials add-on exists for important reasons:
>>
>>
>>
>> * Workarounds for issues encountered by NVDA users when using Windows
>> 10, including various UI Automation issues.
>> * Respond to changes in accessibility of various apps such as
>> removing workarounds put in place in past versions.
>> * Respond to app executable name changes (Microsoft has changed names
>> of at least three universal app executables).
>> * Provide essential features for Windows 10 users, including
>> suggestions announcement, emoji panel support (Fall Creators Update),
>> Edge notification announcements and others.
>> * To prove to Microsoft and third-party universal app developers that
>> accessibility should be a core design criteria for apps, including
>> letting screen reader users use apps to their full potential.
>>
>>
>>
>> Thank you.
>>
>> Cheers,
>>
>> Joseph
>>
>>
>
>
>
>
>


--
search for me on facebook, google+, orkut..
austinpinto.xaviers@...
follow me on twitter.
austinmpinto
contact me on skype.
austin.pinto3










Re: Clarification: last night's remarks, teaching style

Cearbhall O'Meadhra
 

Well said, Joseph!

 

I agree that learning is only really effective if a person has to think through something that is not exactly as it was presented in the learning situation. Their understanding of the basic problem becomes so much clearer and the ability to resolve the situation becomes so much stronger!

 

Keep up the good work!

 

All the best,

 

Cearbhall

 

m +353 (0)833323487 Ph: _353 (0)1-2864623 e: cearbhall.omeadhra@...

 

 

 

 

 

I use the free version of Spam Reader to get rid of spam. The Professional version doesn't have this disclaimer in outgoing emails. Try Spam Reader for free now!

 

 

From: nvda@nvda.groups.io [mailto:nvda@nvda.groups.io] On Behalf Of Joseph Lee
Sent: Monday, June 19, 2017 9:58 PM
To: nvda@nvda.groups.io
Subject: [nvda] Clarification: last night's remarks, teaching style

 

Dear NVDA community:

 

I have received several remarks offlist regarding my comment to Rosemarie last night in regards to asking her what she has learned through the Mail app problem. I’ll take full responsibility of my remarks and tone, as a practical step, I’ll refrain from posting to this list for the rest of the week (and if I have offended folks, my sincere apologies).

 

As for teaching style I tend to employ: perhaps my remark from last night came as a result of my approach to teaching, which calls for students to have willingness to think, or at least, learn to think critically by asking tough questions, have willingness to fail in hopes of learning important lessons, and learn from mistakes. Perhaps this came as a result of my communication studies and argumentation training, being a member of the competitive speech and debate squad, things I’ve observed on various forums where people just believe whatever leaders say, or something else. My overall intention for asking Rosemarie to tell me what she has learned was to get her to think critically about what she has gone through, not just get a problem fixed. If I say I’m satisfied with the resolution of a problem, then this means no future preparations and applications through careful thinking. I personally believe in a community where not only people offer solutions, but also a venue where members can think critically, and I do know from a decade’s worth of experience on various forums that I’m thinking of an ideal community. One thing I personally would like to see is folks teaching novices not only the beauty of NVDA through solutions, but also fostering a sense of taking ownership of a product and thinking about it; in other words, I think it would be best to prepare willing novices for a time in the future where novices themselves would become power users and teach folks not only NVDA, but also to think carefully. Also, personally, I do not want our NVDA community to just be called “a community of users and developers of NVDA” – one thing that sets our community apart from others is unity, and I think it would be beneficial in the long run to add another title: thinking individuals.

 

Thanks.

Cheers,

Joseph