nvda icon indicating copy to clipboard operation
nvda copied to clipboard

Cursor routing on some newer Papenmeier braille displays doesn't move the cursor to the right position

Open ChrisDel35 opened this issue 9 years ago • 11 comments

When I press a routing button on my Braillex EL66S, the cursor is almost at the expected position but two or a few cells too far. For instance, if I press on the first routing button, the cursor is at the third cell.

ChrisDel35 avatar May 30 '16 12:05 ChrisDel35

Bad! Well I don't have a el66s so I can't help fixing it. You can try to install brxcom. It is unfortunately not easy in some cases. Don't know if they ship the brxnvda.dll in current releases. Good Luck.

hss16 avatar Nov 27 '16 19:11 hss16

@hss16, do you have any contacts at Papenmeier that might be able to help with this; e.g. protocol documentation, loan of a display, etc.?

jcsteh avatar Nov 30 '16 06:11 jcsteh

For anyone with the display this is quite an important issue, assigning this a priority 2. However NVAccess does not have one, and so this issue is blocked until we can get more information.

feerrenrut avatar Nov 30 '16 06:11 feerrenrut

@leonardder, do you happen to have one of these displays?

ehollig avatar Nov 21 '17 00:11 ehollig

Any news regarding this issue? Does anyone have gathered more info? I have some contacts at Papenmeier. I could ask for a protocol documentation if it is enough to solve this. Borowing a display will not be possible I guess, but I know some users who would contribute with comprehensive testing on device.

Adriani90 avatar Mar 18 '18 17:03 Adriani90

Hi,

It always behaves the same with NVDA 2018.1 and a Braillex EL66S display.

Have a nice day. Chris D

From: Adriani90 [email protected] Sent: Sunday, March 18, 2018 6:10 PM To: nvaccess/nvda [email protected] Cc: Delaunay Christophe [email protected]; Author [email protected] Subject: Re: [nvaccess/nvda] Cursor routing on some newer Papenmeier braille displays doesn't move the cursor to the right position (#6019)

Any news regarding this issue? Does anyone have gathered more info? I have some contacts at Papenmeier. I could ask for a protocol documentation if it is enough to solve this. Borowing a display will not be possible I guess, but I know some users who would contribute with comprehensive testing on device.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/nvaccess/nvda/issues/6019#issuecomment-374017223, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ASvTqyC26vca0fS1yeMC_N8v2D1wi0Sqks5tfpTSgaJpZM4Ipw-4.

ChrisDel35 avatar Mar 18 '18 18:03 ChrisDel35

@ChrisDel35 there is a brxcom addon for NVDA on their Website. Did you try to install it?

Adriani90 avatar Jun 07 '18 15:06 Adriani90

I have some reports from german users having this problem. Maybe @leonardder or @bramd are interested to take a look at this as well.

Adriani90 avatar Jul 16 '19 13:07 Adriani90

This issue dates from the pre 2019.3 release. I wonder, has anything improved since then?

LeonarddeR avatar May 07 '24 07:05 LeonarddeR

@ChrisDel35, @hozosch, @bdorer, @dave090679 could you test please whether this issue still occurs in NVDA 2024.4 Beta with a Brailex?

Adriani90 avatar Oct 05 '24 10:10 Adriani90

I don't use a Papenmeier-Display

hozosch avatar Oct 05 '24 11:10 hozosch

No updates from braille users since very long time upon request, closing as abandoned. If you are still having this issue, please comment and we can reopen.

Adriani90 avatar Jun 22 '25 11:06 Adriani90