Well, since my posting below, I've now discovered that the read-to-end function has stopped working altogether, and that if I hold down the control key and try to move through the tex by word, with the right- or left-arrow key, the speech is single letter by single letter, not words! And I think this is just in Outlook. I'm wondering if I've got a virus! But there's no noticeable sluggishness in performance that I can detect. I also do not notice this behavior as I compose in the Reply function. The cursor is definitely moving by words using ctrl-left or right arrows. I've even tried rebooting, but the situation is unchanged. I'm too old for this!
Louis Gosselin -----Original Message----- From: Kevin Huber [mailto:[email protected]] Sent: Friday, June 19, 2015 10:03 AM To: gosselin_louis; Window-Eyes Discussion List Subject: Re: Outlook 2013, Win-Eyes 9.0 and reading postings Hi Louis: I believe that amoung the bug fixes in version 9.1 they have improved the read-to-end so that that problem will be fixed, according to the information in the Readme file for version 9.1. Kevin Huber On 6/19/15, gosselin_louis via Talk <[email protected]> wrote: > I've installed Win-eyes 9.0, and have been fumbling around with it for > a day or so, now. I've also altered the Read-to-end hotkey to > ctrl-pause. > I've been noticing that as I open each email message, I regularly hear > the "clang" sound on plain-text messages, but no sound when the > posting is .html. I find that strange. Isn't .html generally > considered to be the much less safe option than plain-text, so why > would you choose to "warn" me about plain-texxt messages. And you > have to admit, that clang sound is a real attention-getter! > > Secondly, I find that sometimes when I open a message and initiate a > read-to-end, nothing happens, no matter how often the command is > re-issued, no matter where you are in the posting, at the top or > further down, it doesn't matter. Nor does it seem to matter whether > the message is .html or .txt. > > Then, nearly as often, the command works on the next message, slick as > grease. This inconsistency of the behavior of Read-to-end is > particularly annoying. Anyone else experiencing this? I do have 9.1 > on order, so shortly I'll know if this situation goes beyond Version > 9.0. Meantime, are there any suggestions or observations? > > Thank you > Louis Gosselin > > > _______________________________________________ > 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/huber.kevin7%40gmail.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
