[nvda] Re: NVDA crash with Microsoft Word

Hi John,
MS Word is a bit annoying because you can't find out where a line starts and stops with out highlighting it. Where as Wordpad and other text controls all have function calls to work out the line easily. I will take a look at the MS Word sayAll because it shouldn't have done that, I definitly know that the sayAll for edit and richEdit seems to be fine.
Whether or not we put it in a virtualBuffer, we still need to know how long the lines are, and we still need to be able to get the cursor to where the person stopped, in the end.
But, I will look in to it when I have the time. I also must re-write sayAll for outlook Express editable HTML messages since currently it does not work there. 

Mick
----- Original Message ----- From: "John Greer" <jpgreer17@xxxxxxxxxxx> 
To: <nvda@xxxxxxxxxxxxx>
Sent: Sunday, January 28, 2007 2:29 AM
Subject: [nvda] NVDA crash with Microsoft Word
I opened up a .doc file in Microsoft Word 2003 and used the say all command of insert down arrow. It read fine for a time then after page 3 of the document I was reading, NVDA crashed on me. It seemed to get caught in an endless loop. Noticing how NVDA was reading the screen, being able to see a little, I noticed that the way that NVDA is reading the document window in a say all is to continuously scan down the screen and highlight the text as it reads. Would it not be a better method to place the window in a virtual buffer and have NVDA read that way like it does for Internet Explorer? Or Once it scans down the page have it stop scanning at the end of the document. 
To post messages to the list send email to
nvda@xxxxxxxxxxxxx
To unsubscribe from the list send a blank message to:
nvda-request@xxxxxxxxxxxxx
with 'unsubscribe' in the Subject field.
Thank you for your continued support of Nonvisual Desktop Access, an open 
source free screen reader for Microsoft Windows:
http://www.kulgan.net/nvda/

Other related posts: