Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some of the error messages in Windows Live Mail 2009 are not spoken by default #2515

Closed
nvaccessAuto opened this issue Jul 8, 2012 · 5 comments
Assignees

Comments

@nvaccessAuto
Copy link

Reported by briang1 on 2012-07-08 09:12
Recentlyy I have been using windows Live Mail 2009 on Windows XP and noticed that when error messages occur, they seem to only read the choice buttons, such as OK. The text in the aleert or error box can be read with nvda/B or using object navigation but the window seems to be being identified as Dialogue. Here is a sample log fragment from a recent snap of nvda and the nvda/F1 output after navigating to the message.

IO - speech.speak (12:08:56):
Speaking - SoC Subject: Re: Tech for social change - event #9 this
Monday, Date: 07/07/2012 09:33 1565 of 1566'

IO - inputCore.InputManager.executeGesture (12:08:57):
Input: kb(desktop):enter
IO - speech.speak (12:08:57):
Speaking Live Mail dialog'
IO - speech.speak (12:08:57):
Speaking button'
IO - inputCore.InputManager.executeGesture (12:09:23):
Input: kb(desktop):NVDA+b
DEBUG - queueHandler.registerGeneratorObject (12:09:23):
Adding generator 1085
IO - speech.speak (12:09:24):
Speaking u'Windows Live Mail dialog'
IO - speech.speak (12:09:24):
Speaking u'graphic'
IO - speech.speak (12:09:24):
Speaking u'There was an error opening this message.\n\nAn
error has occurred. text'

IO - speech.speak (12:09:26):
Speaking u'link'
IO - speech.speak (12:09:26):
Speaking u'OK button'
IO - inputCore.InputManager.executeGesture (12:09:44):
Input: kb(desktop):numpad4
IO - speech.speak (12:09:44):
Speaking [- speech.speak (12:09:44):
Speaking [u'OK'](u'top']
IO)
IO - inputCore.InputManager.executeGesture (12:09:45):
Input: kb(desktop):numpad6
IO - speech.speak (12:09:45):
Speaking [- speech.speak (12:09:45):
Speaking [u'OK'](u'bottom']
IO)
IO - inputCore.InputManager.executeGesture (12:09:49):
Input: kb(desktop):NVDA+numpad7
IO - speech.speak (12:09:51):
Speaking flat review for this object'
IO - inputCore.InputManager.executeGesture (12:09:56):
Input: kb(desktop):NVDA+numpad4
IO - speech.speak (12:09:56):
Speaking [- inputCore.InputManager.executeGesture (12:10:00):
Input: kb(desktop):numpad4
IO - speech.speak (12:10:00):
Speaking [u'top'](u'link']
IO)
IO - speech.speak (12:10:00):
Speaking [- inputCore.InputManager.executeGesture (12:10:01):
Input: kb(desktop):numpad6
IO - speech.speak (12:10:01):
Speaking [u'bottom'](u'blank']
IO)
IO - speech.speak (12:10:01):
Speaking [- inputCore.InputManager.executeGesture (12:10:03):
Input: kb(desktop):numpad4
IO - speech.speak (12:10:03):
Speaking [u'top'](u'blank']
IO)
IO - speech.speak (12:10:03):
Speaking [- inputCore.InputManager.executeGesture (12:10:08):
Input: kb(desktop):NVDA+numpad4
IO - speech.speak (12:10:09):
Speaking [u'There was an error opening this message.\n\nAn error has
occurred. text read only'](u'blank']
IO)
IO - inputCore.InputManager.executeGesture (12:10:21):
Input: kb(desktop):NVDA+numpad4
IO - speech.speak (12:10:21):
Speaking read only'
IO - inputCore.InputManager.executeGesture (12:10:40):
Input: kb(desktop):control+alt+i
INFO - core.main (12:10:49):
Exiting

INFO - globalCommands.GlobalCommands.script_navigatorObject_devInfo
(12:20:07):
Developer info for navigator object:
name: u'There was an error opening this message.\n\nAn error has occurred.'
role: ROLE_STATICTEXT
states: STATE_READONLY
Python object: <NVDAObjects.IAccessible.StaticText object at 0x03D01B90>
Python class mro: (<class 'NVDAObjects.IAccessible.StaticText'>, <class
'NVDAObjects.IAccessible.IAccessible'>, <class 'NVDAObjects.window.Window'>,
<class 'NVDAObjects.NVDAObject'>, <class 'baseObject.ScriptableObject'>,
<class 'baseObject.AutoPropertyObject'>, <type 'object'>)
description: None
location: (212, 173, 197, 39)
value: None
appModule: <'wlmail' (appName u'wlmail', process ID 1060) at address
3cf5eb0>
TextInfo: <class 'NVDAObjects.NVDAObjectTextInfo'>
windowHandle: 2294646L
windowClassName: u'Static'
windowControlID: 1002
windowStyle: 1342308352
windowThreadID: 3372
windowText: u'There was an error opening this message.\n\nAn error has
occurred.'
IAccessibleObject: <POINTER(IAccessible) ptr=0x1aa008 at 3cf2e40>
IAccessibleChildID: 0
IAccessible event parameters: windowHandle=2294646L, objectID=-4, childID=0L
IAccessible accRole: ROLE_SYSTEM_STATICTEXT
IAccessible accState: STATE_SYSTEM_READONLY, STATE_SYSTEM_VALID (64)

I have not at this time tested this with older versions of nvda.
The same seems to be true of other errors, such as when the connection is dropped while downloading from Imap servers.

@nvaccessAuto
Copy link
Author

Comment 2 by briang1 on 2012-11-25 15:24
Its interesting to note that a lot of the alerts and errors this applies to worked fine in Outlook Express, so they obviously changed something.

@nvaccessAuto
Copy link
Author

Comment 3 by briang1 on 2013-05-07 16:29
Has there been any movement on this one? I was reminded of the issue while trying to set this up for a friend as Live mail has better anti spam than Outlook express, even if it is a bit of a pig with many email accounts.
I also note that the folders tree keeps reading as email is coming in, but this is just annoying.

@nvaccessAuto
Copy link
Author

Comment 4 by briang1 on 2015-01-12 12:37
Hi, this problem is still with us, at least on my windows 7 box in this version of Live mail, which I consider to be better than the later one for various reasons. Ie alerts that read in Outlook Express on XP are not read here, and one has to use navigation modes to get at them.

@dkager
Copy link
Collaborator

dkager commented Jul 14, 2017

@LeonarddeR You are WLM wizard. Is there still a working version of this software?
CC @Brian1Gaff

@LeonarddeR
Copy link
Collaborator

WLM is discontinuued and the last version was 2012, not 2009 as @Brian1Gaff pointed out. Closing as won't fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants