Thanks for your response, Vicky. I must have missed your earlier message. I just now went through a series of list messages and found that waiting for that amount of time does allow speech to return. But, as I'm sure you'd agree, that time mounts up.
To respond to another suggestion, Yardbird's method has two drawbacks, if time is a consideration. First, to escape out of a message is one decision, then what to do with it another. Also, when you click on a message, you have to wait a moment to suffer through all the headings. Before this 8.0.2107 upgrade, I'd press control to silence JAWS, then start reading the contents of the next message. On an active list such as this one, skipping through messages in this fashion, either deleting or saving from within the message field, cumulatively saves time.
----- Original Message ----- From: "Vicky Collins" <v-collins@xxxxxxxxxxxxx>I'm not sure if you saw my message of last night where I talked about a similar problem with OE. So, just in case, I'll ask to make sure. When you get that silence after hitting the delete key, are you waiting several seconds, say fifteen or twenty, to see if speech does start? Vicky Collins v-collins@xxxxxxxxxxxxx
----- Original Message ----- From: "Adrian Spratt" <A.Spratt@xxxxxxxxxxxxxxxx>I've had few of the problems some JAWS users have reported with JAWS 8, except for little annoyances like JAWS saying buttons aren't available when, in fact, they are. However, this latest JAWS update has created a new problem in OE. When I go down a list of incoming messages, beginning with the earliest received, JAWS goes silent after the second or third message I delete. I'm referring to the process of reading a message, deleting it, and having the next one open. To get JAWS speaking again, I find I need to press alt-tab out of the message before going back in.
This experience of JAWS going silent is erratic. Sometimes JAWS does read the next message.
One more factor. When I go into the task manager with alt-control-delete, I'm finding that this updated version of JAWS seems to be using even more memory than previous JAWS 8 updates. After I close JAWS to get its memory usage back to a basic level, the OE silence problem occurs less frequently, though it's still present.
Agreed, I should report the problem to FS, but I'm wondering if others are experiencing this same behavior with JAWS 8.0.2107.
A.S.
-- JFW related links: JFW homepage: http://www.freedomscientific.com/ Scripting mailing list: http://lists.the-jdh.com/listinfo.cgi/scriptography-the-jdh.com JFW List instructions: To post a message to the list, send it to jfw@xxxxxxxxxxxxx To unsubscribe from this mailing list, send a message to jfw-request@xxxxxxxxxxxxx with the word unsubscribe in the subject line. Archives located at: //www.freelists.org/archives/jfw If you have any concerns about the list, post received from the list, or the way the list is being run, do not post them to the list. Rather contact the list owner at jfw-admins@xxxxxxxxxxxxxx
