Hi Dave,
Sorry I couldn't reply earlier. It was a pretty busy end of the week
and I'm afraid today won't be much quieter. Well, I don't know. What
makes it challenging is that it's hard to have a fixed shcedule. But
I'll do my best to provide you with a complete log.
Do you want outpkts
[quoted lines by Vincent LE GOFF on 2015/12/18 at 11:16 -0800]
>Do you want outpkts and debug to be active even when keys are being
>pressed? Or should I do two different logs, one with the detection
>(maximum of debugging information) and one just with intpkts and
>brlkeys active to test several
Hi again,
Good news! I haven't done a log yet (just tested the lattest version
very quickly) but most bindings seemed to be correct. The Fn+H key does
display the help. All messages in the help menu are given according to
the QWERTY keyboard. And all seemed to work (I couldn't test them al
Dave Mielke writes:
> [quoted lines by Nicolas Pitre on 2015/12/17 at 13:29 -0500]
>>That calls for another official release I'd say.
> Yes, it certainly does. I still need Aura to confirm the fix too, though.
It works now, thank you!
--
Aura
___
[quoted lines by Vincent LE GOFF on 2015/12/18 at 11:36 -0800]
>One thing that I have been unable to do, although I think it's a matter of
>configuration, is to have the Braille display follow the virtual cursor when
>you move it using the standard keyboard numpad7 to go up and numpad9 to go
>d
I've tested a bit more. The underscore (_) works fine. Actually I
tried most keys on the BrailleSense keyboard and they seemed to work (I
could type from this keyboard without errors).
I was referring to the other keyboard, as a matter of fact. The
computer's. On NVDA and Orca (and I think
Just to verify: The two scroll keys on the left should go up/down by lines. The
wto on the right should pan left/right by braille display widths. So, it should
be:
Lef Up: up one line
Left Down: down one line
Right Up: pan left
Right Down: pan right
That's what I'm expecting. Is tha
>> On Nov 2, 2015, at 2:56 AM, Mario Lang wrote:
>>
>> This looks like systemd. Try "systemctl stop brltty".
>> Sysstemd is indeed a completely new beast. THe inittab as such is gone,
>> as far as I know. systemd does dependency-based booting.
>> So you specify the actual point where BRLTTY sh