Hi,
The fact that the BRLTTY driver failed for five successive attempts is
probably due to the fact I cannot plug the device in at once. Linux runs
in a virtual machine, but when I open it, it attempts to transfer toe
USB port to the virtual machine, so the guest machine can use it instead
of the host machine. This takes some time (about a minute). I need to
unplug and replug the device after the transfer has been effective,
otherwise BRLTTY doesn't detect it.
Actually as it is the driver is very effective. I couldn't test the
time it took to answer very much but it seemed quick (quicker than on
some other devices, I'd admit). My main need was to be able to open the
help menu and preferences menu. Both work fine (and other key
combinations do, as well). So I'd say, for me, it looks great the way
it is.
Thanks again,
Vincent
On 12/19/2015 8:19 PM, Dave Mielke wrote:
[quoted lines by Vincent LE GOFF on 2015/12/19 at 16:43 -0800]
I hope I'm not too much in late.
Not at all. Thanks for capturing those two logs.
I had a major debugging to do on a different product all morning and part of
the afternoon. And it's not even over, but I got a break.
That's fine. We all, myself included, have lives that include many things - not
just this one. There've been plenty of times when others have been waiting for
me to get something done.
I've tried seeing both logs, but I got something really odd.
No, there's nothing odd about either log. A log is evidence - that's all it is.
It only seems to be odd if we have a preconceived idea regarding what that
evidence should be telling us.
The first one (brltty.log) is an extended description when I plug the device
in. It seems that it's not recognized... although it is. I let you decide
what it means.
:-) It probably means that you started brltty about half a minute before you
connected its USB cable. The driver does indeed detect the device just fine,
but only on its sixth attempt. Since there's no evidence of any kind of failure
(other than, without even a warning message, the driver failing to start for
five times), I'm assuming that's because the device wasn't connected until the
driver's sixth attempt.
In any event, this log does confirm that the support that was added for the new
part of the protocol is indeed working correctly. It's also showing me exactly
how long the device is taking to respond to the robe, which is very useful
information.
The second log has been done with less verbosity, to try FN_1, FN_[, FN-{ and
FN-, . However, there seems to be only one key logged. And it doesn't match.
So this second test didn't give much information. Since FN is used internally
by the BrailleSense, perhaps (and only perhaps) these keys didn't send
anything to the console. I would think such is the case, because I got an
alert sound, not from the computer, but from the BrailleSense itself, when I
pressed these keys.
The absence of what we hope we're going to find still is information. This log
is categorically telling me that we can't bind the function key to anything
other than letters. That's exactly what I was wanting to check out.
Still, here are both logs.
Please - and this applies to any and everyone - never hesitate to send me a log
if you don't think it contains helful information. It usually does, and, in the
case that it doesn't, it'll still give me the opportunity to suggest additional
ways to try to gather the sought for data.
Can you think of anything else that you'd like to have supported? Are there any
additional brltty functions that you wish were bound to some key combination?
_______________________________________________
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
