Date   

locked Re: NVDA add on's RSS feed.

 

Brian,
Thanks for the answer!
Again, too bad that I'm not smart enough to do everything you do :)
Now, be sure that I haven't posted it here without making any heffort to find RSS addresses. And well, I found some of them, but it's not always that a website show this option.
But then, as I said, it's just that I'm not smart enough. :)


Cheers,
Marcio AKA Starboy

Sent from a galaxy far, far away.

Follow or add me on Facebook

Em 30/04/2019 11:31, Brian Vogel disse:

On Tue, Apr 30, 2019 at 09:56 AM, marcio wrote:
And I do use Thunderbird as my RSS reader, but ya know, whitout feed addresses it won't do any good.
Marcio,

           You absolutely deserve this snarky response:  "Google is your friend."

           I have used several search engines and searching on the entity name and RSS has either gotten me the RSS link or taken me to the organizations page under which the RSS link can be obtained (which seems to be Podcasts on a number of them).

           This is not rocket science, and it's exactly what web search engines were created for and do best.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1809, Build 17763  

Growth for the sake of growth is the ideology of the cancer cell.

           ~ Edward Abbey

 

 



locked Re: NVDA add on's RSS feed.

 

On Tue, Apr 30, 2019 at 09:56 AM, marcio wrote:
And I do use Thunderbird as my RSS reader, but ya know, whitout feed addresses it won't do any good.
Marcio,

           You absolutely deserve this snarky response:  "Google is your friend."

           I have used several search engines and searching on the entity name and RSS has either gotten me the RSS link or taken me to the organizations page under which the RSS link can be obtained (which seems to be Podcasts on a number of them).

           This is not rocket science, and it's exactly what web search engines were created for and do best.
 
--

Brian - Windows 10 Pro, 64-Bit, Version 1809, Build 17763  

Growth for the sake of growth is the ideology of the cancer cell.

           ~ Edward Abbey

 

 


locked Re: NVDA add on's RSS feed.

 

Too bad I'm not using the ESR version. And I do use Thunderbird as my RSS reader, but ya know, whitout feed addresses it won't do any good.

Thanks anyway :)


Cheers,
Marcio AKA Starboy

Sent from a galaxy far, far away.

Follow or add me on Facebook

Em 30/04/2019 10:40, Robert Kingett disse:

[Edited Message Follows]
[Reason: Included steps on how to get the RSS feed in FF.]

The only web browser that can find and display RSS feeds as a page is FireFox E SR edition. Otherwise, you would have to fiddle with the URL and use a third party RSS reader or an add on for the non E S R version of FireFox. Mozilla claims very few people used the live bookmarks functionality, but the internet has been trying to slowly kill RSS feeds for a while so people have no choice but to subscribe to spammy email lists. Edge does not support finding RSS feeds as far as I know. Chrome does not either, as far as I know. The ESR version of FireFox is the only browser left that can find RSS feeds and display them as a page. To find an RSS feed in FF ESR, do the following. Go to the page or blog in question. Go to your bookmarks menu. Go down until you hear, live bookmarks, expand that menu. Select the feed you want from the resulting list.



locked Re: request for participation in a study

 

As there has been an expansion in the age range for participants, I am posting the revised call for participants:

Hi all,

 

As part of my master’s degree in Linguistics at the University of Cambridge, I am conducting research on how blind and sighted adults understand and interpret language. I am looking for congenitally blind or early blind adults, on the one hand, and sighted adults on the other, aged between 18 and 67, who do not have any additional disabilities, and who grew up in an English speaking country. The survey will take between 40-45 minutes. Participants in the survey will be entered into a draw to win one of four £25.00 amazon.co.uk gift cards. Anyone who wants to participate in the survey please

e-mail me at my academic email address (es777@...), and I will send out the survey.


Enes Sariba
ş
Principal Researcher

--

Brian - Windows 10 Pro, 64-Bit, Version 1809, Build 17763  

Growth for the sake of growth is the ideology of the cancer cell.

           ~ Edward Abbey

 

 


Reaching the comments' section on YouTube video

 

Hi guys,
Quite a while ago I posted here about the very same subject and at that time there was a workaround that really worked like a charm.
Trouble is, it doesn't seem to work anymore.

So, would any of you happen to know of a way to get to the comments' section on a YouTube video in a reliable manner?
Lately, for me, it's been a hit and miss. And honestly, let me tell you, it has been more of a miss than a hit. Really not fun to waste so much time with something that should be easy peasy, as I like to say.

I'm sending this one to the NVDA add-ons list as well, in case someone thinks it'd be a good idea to make an add-on to work with it and give it a solution once and for all.
Were I happen to have enough skills with it I could, should and would very well start such a project.

Cheers,
Marcio.
AKA Starboy

Sent from a galaxy far, far away.

Follow or add me on Facebook


Re: outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list

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

Also make sure that the version of 2016 is fully up to date with all its bits as I found that somewhere along the line there was a version of 2016 that had the mentioned issue.
Brian

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

----- Original Message -----
From: "Gene" <gsasner@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, April 30, 2019 12:33 PM
Subject: Re: [nvda] outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list


Make sure the program is set for object navigation, not screen review. This sounds like a problem caused by screen review being the setting. After using screen review, people should be sure to return to object navigation because not doing so causes problems and some of those problems don't appear to be connected to screen review being the current setting, but they are.

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

From: J.G
Sent: Tuesday, April 30, 2019 6:13 AM
To: nvda@nvda.groups.io
Subject: [nvda] outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list


Hello,

my client uses NVDA screen reader on win10 with outlook 2016 as a mail client. when we've updated NVDA to latest stable version, nvda's focus does not go to next/previous message in message list when pressing up/down key. before I began to help her, she had one of older versions of nvda, I don't know exactly which; but she tells me that it worked fine.
I tried with shift+tab and then tab again to refresh and it sometimes work, sometimes does not. I also tried with word UIA enabled, but there were same results.
any suggestion, how to solve this problem?

thanks in advance.

regards, Jožef


locked Re: NVDA add on's RSS feed.

 
Edited

The only web browser that can find and display RSS feeds as a page is FireFox E SR edition. Otherwise, you would have to fiddle with the URL and use a third party RSS reader or an add on for the non E S R version of FireFox. Mozilla claims very few people used the live bookmarks functionality, but the internet has been trying to slowly kill RSS feeds for a while so people have no choice but to subscribe to spammy email lists. Edge does not support finding RSS feeds as far as I know. Chrome does not either, as far as I know. The ESR version of FireFox is the only browser left that can find RSS feeds and display them as a page. To find an RSS feed in FF ESR, do the following. Go to the page or blog in question. Go to your bookmarks menu. Go down until you hear, live bookmarks, expand that menu. Select the feed you want from the resulting list.


Re: Suspicious log when starting Outlook

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

Now you need to ignore the two addons in the log below as weird stuff goes on even if they are disabled when launching this older copy of word too. It does not seem to result in any problems.
Speaking [LangChangeCommand ('en_GB'), u'Taskbar']
IO - inputCore.InputManager.executeGesture (14:23:25.157):
Input: kb(desktop):control+alt+m
DEBUGWARNING - watchdog._watcher (14:23:25.299):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 150, in executeEvent
File "eventHandler.pyo", line 163, in doPreGainFocus
File "api.pyo", line 145, in setFocusObject
File "api.pyo", line 240, in setNavigatorObject
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 128, in event_becomeNavigatorObject
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 173, in playObject
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 205, in play
File "baseObject.pyo", line 31, in __get__
File "NVDAObjects\IAccessible\__init__.pyo", line 815, in _get_role
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - eventHandler.executeEvent (14:23:25.348):
error executing event: becomeNavigatorObject on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x052574F0> with extra args of {'isFocus': True}
Traceback (most recent call last):
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 128, in event_becomeNavigatorObject
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 173, in playObject
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 205, in play
File "baseObject.pyo", line 31, in __get__
File "NVDAObjects\IAccessible\__init__.pyo", line 815, in _get_role
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init
CallCancelled
IO - speech.speak (14:23:25.362):
Speaking [LangChangeCommand ('en_GB'), u'Desktop list']
DEBUGWARNING - eventHandler.executeEvent (14:23:25.448):
error executing event: gainFocus on <NVDAObjects.IAccessible.sysListView32.ListItem object at 0x052574F0> with extra args of {}
Traceback (most recent call last):
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "C:\Users\Brian\AppData\Roaming\nvda\addons\focusHighlight\globalPlugins\focusHighlight.py", line 519, in event_gainFocus
File "eventHandler.pyo", line 100, in next
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 124, in event_gainFocus
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 173, in playObject
File "C:\Users\Brian\AppData\Roaming\nvda\addons\AudioThemes3D\globalPlugins\audioThemes\__init__.py", line 205, in play
File "baseObject.pyo", line 31, in __get__
File "NVDAObjects\IAccessible\__init__.pyo", line 815, in _get_role
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init
CallCancelled
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.772):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.788):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.792):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.799):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.805):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:25.812):
accRole failed: (-2147418111, 'Call was rejected by callee.', (None, None, None, 0, None))
IO - speech.speak (14:23:25.841):
Speaking [LangChangeCommand ('en_GB'), u'Microsoft Word']
IO - speech.speak (14:23:26.072):
Speaking [LangChangeCommand ('en_GB'), u'unknown']
DEBUGWARNING - NVDAObjects.IAccessible.IAccessible._get_IAccessibleRole (14:23:29.091):
accRole failed: (-2147023179, 'The interface is unknown.', (None, None, None, 0, None))
IO - speech.speak (14:23:29.108):
Speaking [LangChangeCommand ('en_GB'), u'edit multi line']
IO - speech.speak (14:23:29.201):
Speaking [LangChangeCommand ('en_GB'), u'page 1 section 1 align left', u'blank']

It is my belief that the only real reason the two add ons are compaining is that the format of or the data itself is not something expected by them so they benignly throw the error on passing the control back.

In this case it was Word 2002/XP on a windows 7 machine, but I've seen similar results for 2003/7
Interesting but probably harmless.

Brian

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

----- Original Message -----
From: "Ralf Kefferpuetz" <ralf.kefferpuetz@elra-consulting.de>
To: <nvda@nvda.groups.io>
Sent: Tuesday, April 30, 2019 11:19 AM
Subject: Re: [nvda] Suspicious log when starting Outlook


Felix,
Do you have any impact in Outlook when starting up?
I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 10:26
To: nvda@nvda.groups.io
Subject: [nvda] Suspicious log when starting Outlook

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__


Re: Suspicious log when starting Outlook

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

I thought the sourceforge list was discontinued?
Brian

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

----- Original Message -----
From: "Felix G." <constantlyvariable@gmail.com>
To: <nvda@nvda.groups.io>
Sent: Tuesday, April 30, 2019 9:25 AM
Subject: [nvda] Suspicious log when starting Outlook


---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007
(yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems
there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init
CallCancelled
DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in
_get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__


Re: Suspicious log when starting Outlook

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

Could I just interject to say these are pretty common, particularly in older versions of office programs. In the end, most of the time everything sort of tends to recover after a pause. I'm not sure but after the part published you tend to get to that often seen none with zeros after it error.

I see it on say, Word 2003?


I'm thinking its more likely due to the ever changing executables in Office, some use uia some do not and on Outlook this is a much worse case, which is one reason I don't use it.

Brian

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

----- Original Message -----
From: "Quentin Christensen" <quentin@nvaccess.org>
To: <nvda@nvda.groups.io>
Sent: Tuesday, April 30, 2019 10:12 AM
Subject: Re: [nvda] Suspicious log when starting Outlook


Have you got any add-ons running? If you restart NVDA with add-ons
disabled, do you still get these entries?

On Tue, Apr 30, 2019 at 6:25 PM Felix G. <constantlyvariable@gmail.com>
wrote:

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007
(yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems
there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in
findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in
_get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in
findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init
CallCancelled
DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in
_get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available:
http://www.nvaccess.org/shop/

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



Re: outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list

Gene
 

Make sure the program is set for object navigation, not screen review.  This sounds like a problem caused by screen review being the setting.  After using screen review, people should be sure to return to object navigation because not doing so causes problems and some of those problems don't appear to be connected to screen review being the current setting, but they are.
 
Gene

----- Original Message -----
From: J.G
Sent: Tuesday, April 30, 2019 6:13 AM
Subject: [nvda] outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list

Hello,

my client uses NVDA screen reader on win10 with outlook 2016 as a mail client. when we've updated NVDA to latest stable version, nvda's focus does not go to next/previous message in message list when pressing up/down key. before I began to help her, she had one of older versions of nvda, I don't know exactly which; but she tells me that it worked fine.
I tried with shift+tab and then tab again to refresh and it sometimes work, sometimes does not. I also tried with word UIA enabled, but there were same results.
any suggestion, how to solve this problem?

thanks in advance.

regards, Jožef


Re: Suspicious log when starting Outlook

Felix G.
 

Hi,
quirks immediately after starting programs have been a long term issue
for me. This is just one of the cases where I chose to have a look at
the log. I believe these are all instances of issue #8389.
In general, whenever cpu spikes, focus tracking goes flaky on me.
Solidly confirmed across multiple machines running both Win 7 and 10.
Best,
Felix
Best,
Felix

Am Di., 30. Apr. 2019 um 13:16 Uhr schrieb Quentin Christensen
<quentin@nvaccess.org>:


Is this a new issue with 2019.1.1 or can you remember when it started? Or has it always happened?

On Tue, Apr 30, 2019 at 8:27 PM Felix G. <constantlyvariable@gmail.com> wrote:

Hi,
yes, the impact is I often have to alt+tab away and back in to get any
meaningful output.
Best,
Felix

Am Di., 30. Apr. 2019 um 12:19 Uhr schrieb Ralf Kefferpuetz
<ralf.kefferpuetz@elra-consulting.de>:

Felix,
Do you have any impact in Outlook when starting up?
I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 10:26
To: nvda@nvda.groups.io
Subject: [nvda] Suspicious log when starting Outlook

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__








--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

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


Re: Suspicious log when starting Outlook

Ralf Kefferpuetz
 

Felix,
Lemme install Office 2007 on one of my Win7 64bit SP1 VMWare images later on. Then we can see if we got a general problem with Outlook 2007 and NVDA 2019.1.1 or something else specific to your installation...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 12:27
To: nvda@nvda.groups.io
Subject: Re: [nvda] Suspicious log when starting Outlook

Hi,
yes, the impact is I often have to alt+tab away and back in to get any meaningful output.
Best,
Felix

Am Di., 30. Apr. 2019 um 12:19 Uhr schrieb Ralf Kefferpuetz
<ralf.kefferpuetz@elra-consulting.de>:

Felix,
Do you have any impact in Outlook when starting up?
I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 10:26
To: nvda@nvda.groups.io
Subject: [nvda] Suspicious log when starting Outlook

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__







Re: Suspicious log when starting Outlook

Quentin Christensen
 

Is this a new issue with 2019.1.1 or can you remember when it started?  Or has it always happened?


On Tue, Apr 30, 2019 at 8:27 PM Felix G. <constantlyvariable@...> wrote:
Hi,
yes, the impact is I often have to alt+tab away and back in to get any
meaningful output.
Best,
Felix

Am Di., 30. Apr. 2019 um 12:19 Uhr schrieb Ralf Kefferpuetz
<ralf.kefferpuetz@...>:
>
> Felix,
> Do you have any impact in Outlook when starting up?
> I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...
>
> -----Original Message-----
> From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
> Sent: Dienstag, 30. April 2019 10:26
> To: nvda@nvda.groups.io
> Subject: [nvda] Suspicious log when starting Outlook
>
> ---------- Forwarded message ---------
> Von: Felix G. <constantlyvariable@...>
> Date: Fr., 26. Apr. 2019 um 13:56 Uhr
> Subject: Suspicious log when starting Outlook
> To: NVDA screen reader development <nvda-devel@...>
>
>
> Hi,
> this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
> CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
> Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
> The log starts with me pressing enter to launch Outlook from the taskbar.
> Best,
> Felix
>
> IO - inputCore.InputManager.executeGesture (13:45:06.487):
> Input: kb(desktop):enter
> DEBUGWARNING - watchdog._watcher (13:45:09.467):
> Trying to recover from freeze, core stack:
>   File "nvda.pyw", line 233, in <module>
>   File "core.pyo", line 519, in main
>   File "wx\core.pyo", line 2134, in MainLoop
>   File "gui\__init__.pyo", line 1003, in Notify
>   File "core.pyo", line 489, in run
>   File "IAccessibleHandler.pyo", line 897, in pumpAll
>   File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
>   File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
>   File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
>   File "NVDAObjects\__init__.pyo", line 85, in __call__
>   File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
>   File "baseObject.pyo", line 47, in __get__
>   File "baseObject.pyo", line 147, in _getPropertyViaCache
>   File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
>   File "comtypes\__init__.pyo", line 857, in __call__
>
> DEBUGWARNING - core.CorePump.run (13:45:09.467):
> errors in this core pump cycle
> Traceback (most recent call last):
>   File "core.pyo", line 489, in run
>   File "IAccessibleHandler.pyo", line 897, in pumpAll
>   File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
>   File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
>   File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
>   File "NVDAObjects\__init__.pyo", line 85, in __call__
>   File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
>   File "baseObject.pyo", line 47, in __get__
>   File "baseObject.pyo", line 147, in _getPropertyViaCache
>   File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
> Trying to recover from freeze, core stack:
>   File "nvda.pyw", line 233, in <module>
>   File "core.pyo", line 519, in main
>   File "wx\core.pyo", line 2134, in MainLoop
>   File "gui\__init__.pyo", line 1003, in Notify
>   File "core.pyo", line 490, in run
>   File "queueHandler.pyo", line 86, in pumpAll
>   File "queueHandler.pyo", line 53, in flushQueue
>   File "eventHandler.pyo", line 62, in _queueEventCallback
>   File "eventHandler.pyo", line 155, in executeEvent
>   File "eventHandler.pyo", line 92, in __init__
>   File "eventHandler.pyo", line 100, in next
>   File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
>   File "NVDAObjects\__init__.pyo", line 854, in reportFocus
>   File "speech.pyo", line 403, in speakObject
>   File "speech.pyo", line 277, in speakObjectProperties
>   File "baseObject.pyo", line 47, in __get__
>   File "baseObject.pyo", line 147, in _getPropertyViaCache
>   File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
>   File "comtypes\__init__.pyo", line 857, in __call__
>
>
>
>
>
>
>





--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

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


outlook 2016 and NVDA 2019.1.1: nvda's focus does not go to next/previous message after pressing up/down key in message list

J.G
 

Hello,

my client uses NVDA screen reader on win10 with outlook 2016 as a mail client. when we've updated NVDA to latest stable version, nvda's focus does not go to next/previous message in message list when pressing up/down key. before I began to help her, she had one of older versions of nvda, I don't know exactly which; but she tells me that it worked fine.
I tried with shift+tab and then tab again to refresh and it sometimes work, sometimes does not. I also tried with word UIA enabled, but there were same results.
any suggestion, how to solve this problem?

thanks in advance.

regards, Jožef


Re: Announcement of “Filed” Status

Gene
 

If you don't have to use the object navigator for other things, you can have it not follow NVDA as it does what it does in applications and windows.  If the information is always in the same place, if you place it there, then read the current line where the navigator is, or the current word, whichever one provides the information most efficiently, you can read the information with one keystroke on every message you move to.  Instructions I can write won't completely match the new interface of NVDA, I use an older version.  But if you need them, I can give you an idea of how to do this.  If you think what I am describing will do what you want, others will probably send instructions.
 
Gene

----- Original Message -----
Sent: Tuesday, April 30, 2019 1:07 AM
Subject: Re: [nvda] Announcement of “Filed” Status

Brian:
Thank you for your response.
When NVDA reports email messages, it reports the display as if it were in a table; however, one does not need to use the table reading commands to arrow up and down through the list of email messages.
Nevertheless, if one does use the table reading commands, from left to right, NVDA announces the following:
Status (read/unread);
Unknown graphic header status;
Graphic, Row 6, column 2;
No Attachment, Column 3;
name of person who sent the message (Column 4);
Subject of the message;
Filing indicator yes/no (Column 6).
So, NVDA properly reports the “filed status” of the email message; it is just that I need to read over to the 6th column (but it takes more like 9 presses of the read cell to the right command.
JAWS reads this “filed status” automatically, right after the subject of the email message.
I am so glad you mentioned the screen scraping.  We are using an email management tool that attempts to predict the client and matter numbers where email messages are to be filed.  I’m sure this program, an Outlook add-in) is supplying this filed status indicator.
Anyway, one of several reasons why I’ve turned to NVDA is that JAWS is so painfully slow.  Having to wait 10 to 15 seconds between thea nnouncement of an email message’s subject is intolerable.
NVDA, by contrast is nearly instantaneous.
> On Apr 29, 2019, at 3:39 AM, Brian's Mail list account via Groups.Io <bglists@...> wrote:
>
> I'm not sure what you  mean by filed status though. I guess one annoying thing is that Jaws does a lot of things differently. It will no longer read the read status of emails yet it does read the filed status. I'm confused. These attributes in Microsoft software seem to have been a bugbear for many years changing a bit and throwing off routines put in to find them and read them.
> One has to remember here that Jaws is still installing a screenscraper driver whereas NVDA does not.
> Brian
> bglists@...
> Sent via blueyonder.
> Please address personal E-mail to:-
> briang1@..., putting 'Brian Gaff'
> in the display name field.
> ----- Original Message ----- From: "Ed Marquette" <marquette.ed@...>
> To: <nvda@nvda.groups.io>
> Sent: Sunday, April 28, 2019 1:58 PM
> Subject: [nvda] Announcement of “Filed” Status
>
>
> When one reads through the list of email messages in Microsoft Outlook (2013), a number of attributes (probably the correct term is “header fields”) are announced, e.g., “From,” “Received Date,” “Attachment Presence,” and “Size.”
> On our firm’s system, we also have a “Filed Status” indication that either reads “Yes” or “No.”
> If I manually read the cells, Outlook messages are presented in table format), I find that this status indication is presented in what NVDA calls column 6.
> This “Filed” status indication is the second most important feature, for my purposes.
> I have moved it up in Outlook, and JAWS reads it fine.  I cannot, however, get NVDA to read it automatically as I arrow up and down through the inbox. I think I am missing something.
> Any assistance would be appreciated.
>
>
>
>
>
>



Re: Suspicious log when starting Outlook

Felix G.
 

Hi,
yes, the impact is I often have to alt+tab away and back in to get any
meaningful output.
Best,
Felix

Am Di., 30. Apr. 2019 um 12:19 Uhr schrieb Ralf Kefferpuetz
<ralf.kefferpuetz@elra-consulting.de>:


Felix,
Do you have any impact in Outlook when starting up?
I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 10:26
To: nvda@nvda.groups.io
Subject: [nvda] Suspicious log when starting Outlook

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__







Re: Suspicious log when starting Outlook

Ralf Kefferpuetz
 

Felix,
Do you have any impact in Outlook when starting up?
I'm wondering if this is not only the normal behavior when NVDA is dealing with the Outlook splash screen during startup...

-----Original Message-----
From: nvda@nvda.groups.io <nvda@nvda.groups.io> On Behalf Of Felix G.
Sent: Dienstag, 30. April 2019 10:26
To: nvda@nvda.groups.io
Subject: [nvda] Suspicious log when starting Outlook

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007 (yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init CallCancelled DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in _get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__


Re: Suspicious log when starting Outlook

Felix G.
 

Hi Quentin,
nope, no add-ons here.
All the best,
Felix

Am Di., 30. Apr. 2019 um 11:12 Uhr schrieb Quentin Christensen
<quentin@nvaccess.org>:


Have you got any add-ons running? If you restart NVDA with add-ons disabled, do you still get these entries?

On Tue, Apr 30, 2019 at 6:25 PM Felix G. <constantlyvariable@gmail.com> wrote:

---------- Forwarded message ---------
Von: Felix G. <constantlyvariable@gmail.com>
Date: Fr., 26. Apr. 2019 um 13:56 Uhr
Subject: Suspicious log when starting Outlook
To: NVDA screen reader development <nvda-devel@lists.sourceforge.net>


Hi,
this is on Win 7 64 bit, NVDA 2019.1.1, when launching Outlook 2007
(yes, I know, this is old).
CPU is quadcore 3,10 GHz, no rocket by today's standards but also no snail.
Could anyone please suggest what this log excerpt indicates? Seems
there's a lot of freezing/unfreezing.
The log starts with me pressing enter to launch Outlook from the taskbar.
Best,
Felix

IO - inputCore.InputManager.executeGesture (13:45:06.487):
Input: kb(desktop):enter
DEBUGWARNING - watchdog._watcher (13:45:09.467):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 807, in _get_IAccessibleRole
File "comtypes\__init__.pyo", line 857, in __call__

DEBUGWARNING - core.CorePump.run (13:45:09.467):
errors in this core pump cycle
Traceback (most recent call last):
File "core.pyo", line 489, in run
File "IAccessibleHandler.pyo", line 897, in pumpAll
File "IAccessibleHandler.pyo", line 620, in processGenericWinEvent
File "IAccessibleHandler.pyo", line 532, in winEventToNVDAEvent
File "NVDAObjects\IAccessible\__init__.pyo", line 46, in
getNVDAObjectFromEvent
File "NVDAObjects\__init__.pyo", line 85, in __call__
File "NVDAObjects\IAccessible\__init__.pyo", line 411, in findOverlayClasses
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "watchdog.pyo", line 202, in _COMError_init
CallCancelled
DEBUGWARNING - watchdog._watcher (13:45:10.809):
Trying to recover from freeze, core stack:
File "nvda.pyw", line 233, in <module>
File "core.pyo", line 519, in main
File "wx\core.pyo", line 2134, in MainLoop
File "gui\__init__.pyo", line 1003, in Notify
File "core.pyo", line 490, in run
File "queueHandler.pyo", line 86, in pumpAll
File "queueHandler.pyo", line 53, in flushQueue
File "eventHandler.pyo", line 62, in _queueEventCallback
File "eventHandler.pyo", line 155, in executeEvent
File "eventHandler.pyo", line 92, in __init__
File "eventHandler.pyo", line 100, in next
File "NVDAObjects\__init__.pyo", line 966, in event_gainFocus
File "NVDAObjects\__init__.pyo", line 854, in reportFocus
File "speech.pyo", line 403, in speakObject
File "speech.pyo", line 277, in speakObjectProperties
File "baseObject.pyo", line 47, in __get__
File "baseObject.pyo", line 147, in _getPropertyViaCache
File "NVDAObjects\IAccessible\__init__.pyo", line 912, in
_get_keyboardShortcut
File "comtypes\__init__.pyo", line 857, in __call__



--
Quentin Christensen
Training and Support Manager

Official NVDA Training modules and expert certification now available: http://www.nvaccess.org/shop/

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


locked Re: NVDA add on's RSS feed.

 

While we are on this (and I know it's not an NVDA thing, just thought I'd ask on this thread):
Is there any way of getting a certain RSS from a website?
For instance I have the www.thisisacool.site.
I want to get the RSS (that is, the link for this RSS), of course assuming this site has one.
Then what should I do to get it?

Cheers,
Marcio AKA Starboy

Sent from a galaxy far, far away.

Follow or add me on Facebook

Em 28/04/2019 15:14, Robert Kingett disse:

[Edited Message Follows]
[Reason: Included the RSS feed.]

This RSS feed will show you new add ons published but it will not group 
add ons by last updated. To check for updates, get the add on updater.

https://addons.nvda-project.org/index.en.rss

Add ons are posted manually to this list as well. Mods have not integrated the feed into this group, so subscribe to the feed above.