thanks. Here is the ticket by NVDA for your reference in case ; http://community.nvda-project.org/ticket/4147
On Tue, Jun 17, 2014 at 5:58 PM, Samuel Thibault < [email protected]> wrote: > Siju Samuel, le Tue 17 Jun 2014 17:52:30 -0500, a écrit : > > thanks I will try with filter. One clarification I have is after > installing > > libus filter, do I need to run brltty.inf at the device plug point? > > No! That would make the device use the libusb-win32 driver, which you > don't want since you want to use the manufacturer's driver for NVDA. > > > What is the difference in set up related to brltty for using > > brltty driver vs filter? > > brltty does not care, libusb-win32 handles the difference for it. > > > >>> When I used NVDA along with brltty, it was not able to get any input > from > > the > > >>> refresh braillle display. > > >>IIRC you already discussed the issue with Dave: it's a problem of NVDA > > >>not interpreting key events from BRLTTY. > > > > No I did not discuss this. But with a quick search I found the > following NVDA > > ticket; which suggests they are waiting for BRLTTY5.1 precompiled > packages to > > perform further development. Probably BRLTTY5.1_libubs too. (FYI) > > Well, if I could afford sleeping only a couple of hours per day, I would > have time to do it, I don't happen to be able to afford it :/ > > Samuel > _______________________________________________ > This message was sent via the BRLTTY mailing list. > To post a message, send an e-mail to: [email protected] > For general information, go to: http://mielke.cc/mailman/listinfo/brltty >
_______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://mielke.cc/mailman/listinfo/brltty
