[duxhelp] Re: DBT 10.5, Beta 5
- From: "Mark Mercer" <markm@xxxxxxxxxxxx>
- To: <duxhelp@xxxxxxxxxxxxx>
- Date: Thu, 12 Aug 2004 09:39:22 -0400
Hi Caryn & Peter and all,
When entering codes using CTRL-[, h1, h2 etc..., If you enter the start code
the text will reflect the change, when you position your cursor to insert the
end code and enter the end code, press return to enter the end code and the
Braille display on the Braille Lite 40 goes blank. You have to up or down
arrow 10 -15 times before you see any text. To fix the problem you have to
refresh the text by adding a text entry and then deleting it or vise versa.
Best Regards,
Mark
----- Original Message -----
From: Caryn Navy
To: duxhelp@xxxxxxxxxxxxx
Sent: Wednesday, August 11, 2004 6:08 PM
Subject: [duxhelp] Re: DBT 10.5, Beta 5
Hello all. I was out of the office for much of Wednesday. Christine, J.R.,
and Mark, thanks for your reports on the JAWS script files. I'm checking out
all these issues and hope to get them fixed in the next DBT that we build.
Sincerely,
Caryn
-----Original Message-----
From: duxhelp-bounce@xxxxxxxxxxxxx [mailto:duxhelp-bounce@xxxxxxxxxxxxx]On
Behalf Of Mark Mercer
Sent: Wednesday, August 11, 2004 1:26 PM
To: duxhelp@xxxxxxxxxxxxx
Subject: [duxhelp] DBT 10.5, Beta 5
Hi All,
Re: version 10.5, build 8/10/04
Has the following already been addressed?
JAWS Script Bugs?:
Using a Braille Lite 40 with JAWS 5.0.844 and Windows XP Home SP1. Have
noticed 2 bugs. First, the top-of-window and bottom-of-window commands
actually read the first and last lines of text shown on the screen, rather than
the top and bottom lines of the window (i.e., title bar and status line).
Second, Braille navigation keys do not work in dialog boxes using line mode,
and edit fields are not labeled. I would imagine this to be true of error
messages, as I have experienced the same problem reading error messages in the
version from Beta four 7/6/04. Neither problem occurs on another computer,
running JAWS 4.02 and Windows 98SE (using the same BLT40).
Some DOS text files are incorrectly identified in the importer as Macintosh
text files; one must change this setting manually. These files may have been
saved as MS-DOS format from WordPerfect or Word (various versions).
Best Regards,
Mark
Other related posts:
