[brailleblaster] Re: Screen Reader Line Problem
- From: Keith Creasy <kcreasy@xxxxxxx>
- To: "brailleblaster@xxxxxxxxxxxxx" <brailleblaster@xxxxxxxxxxxxx>
- Date: Wed, 22 May 2013 20:38:37 +0000
Good point. I'm working on it and think I have a solution in BB but it isn't
quite right yet.
They are not going to make this easy. :)
Keith Creasy
Software Developer
American Printing House for the Blind
KCreasy@xxxxxxx
Phone: 502.895.2405
Skype: keith537
From: brailleblaster-bounce@xxxxxxxxxxxxx
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Vic Beckley
Sent: Wednesday, May 22, 2013 3:26 PM
To: brailleblaster@xxxxxxxxxxxxx
Subject: [brailleblaster] Re: Screen Reader Line Problem
Keith,
I think it needs to be fixed in BB not just in JAWS. Not quite everyone uses
JAWS.
Best regards from Ohio,
Vic
From:
brailleblaster-bounce@xxxxxxxxxxxxx<mailto:brailleblaster-bounce@xxxxxxxxxxxxx>
[mailto:brailleblaster-bounce@xxxxxxxxxxxxx] On Behalf Of Keith Creasy
Sent: Wednesday, May 22, 2013 2:17 PM
To: brailleblaster@xxxxxxxxxxxxx<mailto:brailleblaster@xxxxxxxxxxxxx>
Subject: [brailleblaster] Screen Reader Line Problem
OK, I see what's happening and we can fix it. I'm trying to decide the best way.
I'm using JAWS and on the up/down arrow keys it is calling getText with the
ACC.type set to TEXT_BOUNDARY_ALL (5). TEXT_BOUNDRY_LINE (4) is probably what
it should be using. Maybe this can be fixed in JAWS by setting the class
configuration?
Keith Creasy
Software Developer
American Printing House for the Blind
KCreasy@xxxxxxx<mailto:KCreasy@xxxxxxx>
Phone: 502.895.2405
Skype: keith537
Other related posts:
