There is indeed the rub.  Hard coding a list of known screen readers is at best 
a bit of a hack.  It does not take into account that new products may be 
introduced.  It also does not take into account the possibility that some 
screen reader may change the name of the executable file between versions.  
It's also a bit arrogant for someone to suggest to another programmer what 
would be easy without having knowledge about how a program actually does work.  
This would be the kind of thing that would cause a big deal the first time it 
broke.  
  ----- Original Message ----- 
  From: K. Matthew 
  To: [email protected] 
  Sent: Friday, September 12, 2008 2:36 PM
  Subject: RE: WE 7 Beta 3 issues and priorities


  Who said it would be controlling?  It is a simple code. 

   

  1.       You start up window eyes

  2.         Before full start up it checks for said name screen reader

  3.         If said name screen reader is not running  It would skip to line 5

  4.         If yes,  ask user to shut down said name screen reader and restart 
window eyes

  5.         Start up window eyes if said screen reader is not present, and 
continue with normal operations of check syssum and load files

   

  Of course the actual code would be longer then that.  But, it gives a general 
idea of would would happen before window eyes starts up fully.  As it already 
checks before starting up if you have the Video Intercept driver correctly 
installed anyways.  This would just make sure one les thing is going to cause a 
problem.

   

  Matt.

   

  From: Stephen Clower [mailto:[EMAIL PROTECTED] 
  Sent: Friday, September 12, 2008 2:12 PM
  To: gw-info-gwmicro.com
  Subject: Re: WE 7 Beta 3 issues and priorities

   

  That is indeed a recipe for disaster. I would be weary of my software being 
able to potentially control other programs. Say, for instance, that I had JFW, 
and it could interrupt the Window-Eyes boot sequence. Conceivably, Freedom 
Scientific could wreck my Window-Eyes install whenever they wanted. Given what 
their PR department's done lately, I wouldn't put it past them anymore.

  Another potential solution is to have all screen reader installs always ask 
you if you want them to load at startup. At least with something like a quick 
install, it would be harder to accidentally ignore the potential screen reader 
conflicts.

  Best regards,
  Steve





If you reply to this message it will be delivered to the original
sender only.  If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be 
searched through and sorted using the search
form at the bottom of the page. 

If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body 
of the message.


If you reply to this message it will be delivered to the original
sender only.  If your reply would benefit others on the list and
your message is related to GW Micro, then please consider sending
your message to [email protected] so the entire list will receive it.

All GW-Info messages are archived at http://www.gwmicro.com/gwinfo, and can be 
searched through and sorted using the search
form at the bottom of the page.

If you wish to unsubscribe from this list, send a message to
[EMAIL PROTECTED] and include leave gw-info in the body
of the message.

Reply via email to