[BRLTTY] Yet another brltty windows build: 3.10-7

[James Teh]

On 12/11/2008 9:38 PM, Samuel Thibault wrote:
> I have to say I've never really even tried to understand how
> libusb-win32 works, as the documentation is poor, to say the least.
I can't argue there. :)

> I
> have just followed the inf-wizard documentation, which doesn't talk
> about the filter.  I guess it is install-filter.exe which needs to be
> run, does that install anything or need any other file?
Looks like you run install-filter.exe -i to install and 
install-filter.exe -u to uninstall. However, I had to read their 
installer source code to figure this out, as install-filter.exe doesn't 
seem to provide any command line help. I'm not sure what files it 
requires...

>> the libusb-win32 filter is ideal if you have a driver already
>> installed, while the libusb-win32 driver is ideal if you don't.
> Ok, makes a lot of sense.
It's rather confusing to explain to most users, though. :) I suspect the 
majority of users will probably have the manufacturer provided Windows 
drivers installed, so the filter is probably best for most. 
Unfortunately, as I've mentioned several times before, the filter seems 
to have some rather serious problems. (The driver could have these as 
well; I've never tested it.)

>> This is one of the reasons I am tempted to simply implement drivers
>> for displays directly in NVDA, as silly and redundant as this is.
> You mean using the interface provided by the drivers, or using the
> virtual serial port?
The API, where provided. However, many displays don't provide this, so 
we'd have to do virtual serial stuff there.

-- 
James Teh
Email/MSN Messenger/Jabber: jamie at jantrid.net
Web site: http://www.jantrid.net/