Re: There are at least four ways that screen readers determine what to speak in most cases Windows tells the screen reader that something happened on a window then then the screen reader asks the prog

[Pamela Dominguez via Talk]

The message wasn't blank.   It's just that he put the message in the 
subjectline instead of where it should have gone.  Pam.


-Original Message- 
From: Rick Thomas via Talk

Sent: Sunday, February 28, 2016 5:04 AM
To: 'Jonathan C. Cohn' ; 'Window-Eyes Discussion List' ; 'Manny'
Cc: 'WE SUPPORT'
Subject: RE: There are at least four ways that screen readers determine what 
to speak in most cases Windows tells the screen reader that something 
happened on a window then then the screen reader asks the program that owned 
the window what happen? UIA is the most


Hi: Jonathan, looks like your message was blank.
The fact that WindowEyes can crash the system, lock it up, when no reply is
found from a called method or object is a bug in WindowEyes.
In programming, especially when programming against third party apps, you
put a request for anything in a test block so that if the object or method
does not return an expected value you handle the error and continue
processing.
This is not bad code but a bug in WindowEyes.
Their well may be a way around the quote no response by getting the
information from someplace else or by using some other feature of the third
party program but to lock up the screen reader because of a problem in a
third party program is a bug pure and simple.
I have said this when I analyzed a similar situation for Internet Explorer
11, your fault, my fault, nobodys fault just fix it AI Squared.
That means testing the objects and methods within a very short timed bcode
block or a try catch block or something to that effect and handling any
error message or no response situation in the WindowEyes program.
As for no response to AI Squared from third party vendors, you have a legal
department don't you - use them.
Rick USA

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.


For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/geodom%40optonline.net.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com 


___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com

RE: There are at least four ways that screen readers determine what to speak in most cases Windows tells the screen reader that something happened on a window then then the screen reader asks the prog

[Sky Mundell via Talk]

Hi Rick, and Jonathan, and everybody.  I personally haven't encountered
those lock-up problems that you guys are experiencing. As an adaptive
technology trainer working on a 6 month contract, ending in March, I have to
say I have been teaching Window-Eyes to sighted staff, and volunteers and
everything works like a charm with no hickups on their end.

-Original Message-
From: Talk [mailto:talk-bounces+skyt=shaw...@lists.window-eyes.com] On
Behalf Of Rick Thomas via Talk
Sent: Sunday, February 28, 2016 2:05 AM
To: 'Jonathan C. Cohn'; 'Window-Eyes Discussion List'; 'Manny'
Cc: 'WE SUPPORT'
Subject: RE: There are at least four ways that screen readers determine what
to speak in most cases Windows tells the screen reader that something
happened on a window then then the screen reader asks the program that owned
the window what happen? UIA is the most

Hi: Jonathan, looks like your message was blank.
The fact that WindowEyes can crash the system, lock it up, when no reply is
found from a called method or object is a bug in WindowEyes.
In programming, especially when programming against third party apps, you
put a request for anything in a test block so that if the object or method
does not return an expected value you handle the error and continue
processing.
This is not bad code but a bug in WindowEyes.
Their well may be a way around the quote no response by getting the
information from someplace else or by using some other feature of the third
party program but to lock up the screen reader because of a problem in a
third party program is a bug pure and simple.
I have said this when I analyzed a similar situation for Internet Explorer
11, your fault, my fault, nobodys fault just fix it AI Squared.
That means testing the objects and methods within a very short timed bcode
block or a try catch block or something to that effect and handling any
error message or no response situation in the WindowEyes program.
As for no response to AI Squared from third party vendors, you have a legal
department don't you - use them.
Rick USA

___
Any views or opinions presented in this email are solely those of the author
and do not necessarily represent those of Ai Squared.

For membership options, visit
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/skyt%40shaw.ca
.
For subscription options, visit
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com

Re: There are at least four ways that screen readers determine what to speak in most cases Windows tells the screen reader that something happened on a window then then the screen reader asks the prog

[Reg Webb via Talk]

Rick
The entire message was in the subject line. 
-- 
Reg


On Sun, 28 Feb 2016 05:04:47 -0500
Rick Thomas via Talk  wrote:

> Hi: Jonathan, looks like your message was blank.
> The fact that WindowEyes can crash the system, lock it up, when no reply is
> found from a called method or object is a bug in WindowEyes.
> In programming, especially when programming against third party apps, you
> put a request for anything in a test block so that if the object or method
> does not return an expected value you handle the error and continue
> processing.
> This is not bad code but a bug in WindowEyes.
> Their well may be a way around the quote no response by getting the
> information from someplace else or by using some other feature of the third
> party program but to lock up the screen reader because of a problem in a
> third party program is a bug pure and simple.
> I have said this when I analyzed a similar situation for Internet Explorer
> 11, your fault, my fault, nobodys fault just fix it AI Squared.
> That means testing the objects and methods within a very short timed bcode
> block or a try catch block or something to that effect and handling any
> error message or no response situation in the WindowEyes program.
> As for no response to AI Squared from third party vendors, you have a legal
> department don't you - use them.
> Rick USA
> 
> ___
> Any views or opinions presented in this email are solely those of the author 
> and do not necessarily represent those of Ai Squared.
> 
> For membership options, visit 
> http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/regwebb%40btinternet.com.
> For subscription options, visit 
> http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
> List archives can be found at 
> http://lists.window-eyes.com/private.cgi/talk-window-eyes.com

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com

RE: There are at least four ways that screen readers determine what to speak in most cases Windows tells the screen reader that something happened on a window then then the screen reader asks the prog

[Rick Thomas via Talk]

Hi: Jonathan, looks like your message was blank.
The fact that WindowEyes can crash the system, lock it up, when no reply is
found from a called method or object is a bug in WindowEyes.
In programming, especially when programming against third party apps, you
put a request for anything in a test block so that if the object or method
does not return an expected value you handle the error and continue
processing.
This is not bad code but a bug in WindowEyes.
Their well may be a way around the quote no response by getting the
information from someplace else or by using some other feature of the third
party program but to lock up the screen reader because of a problem in a
third party program is a bug pure and simple.
I have said this when I analyzed a similar situation for Internet Explorer
11, your fault, my fault, nobodys fault just fix it AI Squared.
That means testing the objects and methods within a very short timed bcode
block or a try catch block or something to that effect and handling any
error message or no response situation in the WindowEyes program.
As for no response to AI Squared from third party vendors, you have a legal
department don't you - use them.
Rick USA

___
Any views or opinions presented in this email are solely those of the author 
and do not necessarily represent those of Ai Squared.

For membership options, visit 
http://lists.window-eyes.com/options.cgi/talk-window-eyes.com/archive%40mail-archive.com.
For subscription options, visit 
http://lists.window-eyes.com/listinfo.cgi/talk-window-eyes.com
List archives can be found at 
http://lists.window-eyes.com/private.cgi/talk-window-eyes.com