NOTEPAD:
I have a document of some 500 lines. Pressing CTRL-F - to search for text - and 
then filling in my search term, then pressing Enter, then Escape. WE now 
reports the first occurance of my search term, and the line shows up on my 
Braille display. Pressing F3, to repeat the search, the speech repeats the next 
occurance, but the Braille display is still showing the first. Consequtive 
presses on F3, this behavior repeats itself. The Braille display will 
permanently show the first occurance, no matter how far down in the text the 
speech (and the cursor) operates. Soon as I press one of the cursor keys, the 
Braille display jumps to the cursor, and starts acting normal again.

ALT-TABBING BETWEEN SEVERAL WINDOWS:
This has been the case prior to 7.2. If I have a good handful of windows 
opened, particularly several webpages, and then start tabbing through the whole 
list, something seems to get messed up. Say, for instance, you have a total of 
15 webpages open, and 5 other widnows (like outlook Express, Notepad, Excell, 
and a music player).  OK, so you are at webpage 1, and want to Alt-Tab to your 
music player (which might be number 8, down the list). You start to Alt-Tab, 
and in the beginning, everything is OK, WE reports every window title as it 
should. But all the certain, you hear your Webpage1, then Wbpage2, then 
Webpage3 over again; even if you only have pressed Alt-Tab say 6 times. Ending 
the Alt-Tab sequence here, when Webpage3 was just announced, you find that you 
actually are in Notepad, Which happend to be the number seven in the list. Hope 
this explaination makes sense, and is reproducable. I really find it anoying, 
when I can't trust which window i am landing on, when Alt-Tabbing through the 
list of opened applications. Time to have this fixed :)

OUTLOOK EXPRESS:
Writing a longer message, using the built-in editor. After finishing writing, I 
go to the top, by Ctrl-Home. Then pressing Ctrl-Shift-R, to have We reading the 
document to me, for proof-reading. In the beginning it works fine, but all the 
certain, the speech terminates, even in the middle of a phrase. Scrolling up 
and down with the cursor keys, might not help. If I send the message, it 
proves, that the whole message was there, even if WE 'locked up' in the middle 
of the proof-reading. Why is this? I went to the WE controlpanel, and into the 
set-manager, and ran the update prcedure. It reports, 210 files, 0 converted; 
which I take, means that all my sets are up-to-date.

EXCEL 2003:
Still getting the following behavior: Quite often, when filling in the 
information in a cell, particularly when writing text, the two first characters 
are not spoken. Using the cursor keys, or moving to next cell, then back again, 
it proves that all the typed characters were registerd by Excel. Why does the 
speech not report the first two characters, when filling in the cell? I have 
teh window maximized, and have tried to update the screen (ins-backslash), even 
alt-tabbed to another window, and back again. All of this, to no avail.

The Braille display is not behaving correctly, when editing formulas. I have 
pointed this out, several times. Really hoped 7.2 would hold a fix for it, but 
can't see any change in behavior. When editing a formula, in Excel 2003, the 
speech reads the formula correctly, but the Braille display does not follow the 
editing. I.e, your formula reads B123:c234. You open the formula widnow - press 
Alt-I, then F - and start to edit. Press End, then backspace twice. The screen 
would read B123:C2, but the Braille display still shows B123:C234. Do whatever 
changes you want to your formula, the Braille display stubbornly keeps showing 
the same old formula (B123:c234). It is anoying, and totally unacceptable, when 
you can't rely on the Braille display. What makes this bug not fixed yet, I 
don't know, but I reported this already back with teh Beta of 7.0... :)

HARD DRIVE STUFF:
I have two hard drives on my computer, both being SATA II drives. They are 
defined as Drive C, and Drive E:. Window-Eyes is installed on Drive C:.
When Drive E: hasn't been used for a few minutes, it spins down, as a matter of 
power management. Being installed on drive C:, WE keeps working just fine. But 
if there is a call for drive E:, and the speech is in the middle of a word, 
Eloquence keeps stuttering on a vowel for all the time, it takes to spin up 
drive E:. I didn't find this to be a problem prior to 7.2, and wonder why this 
happens.



--
I am using the free version of SPAMfighter.
We are a community of 7 million users fighting spam.
SPAMfighter has removed 1267 of my spam emails to date.
Get the free SPAMfighter here: http://www.spamfighter.com/len

The Professional version does not have this 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.

GW-Info messages are archived at http://www.gwmicro.com/gwinfo. You can manage 
your list subscription at http://www.gwmicro.com/listserv.

Reply via email to