Has anyone else seen crashes with the Braille Extender add-on and NVDA 2018.3.2? I just got this braille display and this looked kind of neat. I’m using a Brailliant BI 40.

It works fine here. I just tested with Firefox 62.0.3 on the recent Windows 10 updates, and it seems to work fine.

I get no errors here. Pressing numpad 5 twice quickly spells the current word as expected.

Has anyone else noticed that cursor routing buttons don’t work to route the cursor in edit fields sometimes, and the braille display sometimes doesn’t reflect the currently-being-typed input? Have I g

Alright, I’ll check to see if I have something misconfigured.

The last I heard, it would only be available posibly for preorder in the UK. You could sign up to potentially have yours shipped by the 31st of October, 2019. They are apparently only making 40 of the

I don't know about BRLTTY for NVDA or narrator, because I've only ever used it on Linux. Hower, I do know that you can use the braille extender add-on to read .brf files. I just open them in wordpad o

You could try the Linux for Windows subsystem, but again that's for another list/topic. I'll poke around. I don't have an older display to test with exactly, but I can mess around with BRLTTY with wha

Yes, the braille extender add-on has a specific .brf mode as well as a keystroke to hide dot 7 and 8, but I just toggle the .brf mode on when I am in a braille file and it works fine. I just realized

Yes, this Dell has all of those as well. If I'd known that I'd have kept my doubletalk LT around when I moved.

I’m surprised that your computer still runs if it’s old enough to have shipped with XP. I’d guess you couldn’t update most things, and that if you got new hardware it’s likely to run badly, if at all.

In limited testing, it seemed to work quite well, so far. Except that Braille Extender doesn't load. I'm wondering if it's better to have that in NVDA core anyway, as the built-in braille support seem

The only add-ons I usually use are braille extender and the Windows 10 essential ones, and the add-on updater, but it looks like all of those are either being updated, or already work fine with the ne

Alright, well, I'll poke around for another solution then, or see what can be done. At least there is time, and I do think the Python 3 changes are necessary. It is great the good work everyone is doi

It is definitely a bug! I can duplicate it here as well as a couple other things. But the add-on will likely no longer work as of 2019.3 because of the move to Python 3 support, so we may have to find

I wrote to the developer, but I didn't check the git hub page, I was just saying it may not work with Python 3 because I wasn't sure if he'd have time to work on it. But we'll see what we can do. I wi

Yes, that's what I saw, too, when I briefly looked at it. It requires syntax changes and some testing, and the author may not have time to do it. How much of the functionality should we put in NVDA co

Yes, that makes sense. He did say somewhere that the documentation needs to be improved. We could see if that’s possible, assuming the add-on will get updates once they move to Python 3.

Does setting NVDA Synthesizer output to a specific sound card help? Normally it defaults to Microsoft sound mapper, but maybe it is doing something odd. So maybe if you give it a specific card it will

I prefer the Jaws dots 7 and 8 approach though I can usually tell where a link is from context, but also NVDA has a lot of weird indicators in places it shouldn't especially when using UEB. I'm pretty