[BRLTTY] Changing BRLTTY key mapping [repost]

[Vincent LE GOFF]

Thank you Dave.


I believe that the ht (HandyTech) driver is pretty much centralized on 
BRLTTY.  Meaning that most displays of this brand will have the same 
features except for slight modifications.  I am using the Actilino (alo) 
and have been testing the ActiveBraille (ab40).  As it is, it sounds 
like the default mapping is not correct for either of these devices.  By 
"correct", I mean that when using them in standalone mode (as Braille 
notetakers) or plugged to a screen reader on Windows, simple mapping 
(for navigation, for instance) is different.  However, by altering the 
problematic files, it would also affect a lot of other handytech 
displays for which the mapping might be more accurate, I have no idea.


For instance, to go to the next Braille window (which is something one 
does very often, admittedly), the default key mapping is "Right Triple 
Action Key center (TRC)".  On other devices, it might be one key, but on 
the Actilino and ActiveBraille, that's two keys you have to press 
simultaneously. So only moving the Braille window requires two key 
presses (fortunately, they are close).  In standalone (which should be 
the reference, I imagine), only Right Triple Action Key down (TRD) or 
Left Triple Action Key down (TLD) are necessary (either, not both at the 
same time).  The Adctilino and ActiveBraille have four navigation keys, 
two on either side of the display.  This is quite common for other 
displays as well.  So the Triple Action Key Center requires the press of 
Triple Action Key Up + Triple Action Key Down.  And that's not really great.


But I insist: I have no idea how the other devices behave, so I prefer 
to make my modification just for my BRLTTY installation. Other handytech 
users might be well-used to the current setup and unwilling to shift, 
which I completely understand.


Thank you again,


Vincent


On 3/9/2018 12:29 PM, Dave Mielke wrote:
> [quoted lines by Vincent LE GOFF on 2018/03/09 at 07:44 +0100]
>
>> So I've got my new Braille display, and would like to update its key
>> bindings so it'd behave a bit closer from what it does in standalone,
>> and how it behaves with other screen readers.
> Which braille device do you have? Is there something wrong with brltty's
> bindings for it that you think we should consider fixing?
>
>> In the README.customize, there's no mention of respecting the directory
>> structure.  However, the file I want to edit is in input/ht/rockers.kti .  So
>> do I need to create a ht folder in /etc/xdg/brltty and the rockers.kti file in
>> it, or do I just add a /etc/xdg/brltty/rockers.cti file?
> Put it right in brltty's xdg directory. Don't create a directory structure
> underneath it.
>
>> I don't want to create conflicts with other drivers, if possible.
> Yes, that's a risk. It was done this way in order to make it as easy as
> possible.
>
>> As I mentioned, I would like to change rockers.kti .  My actual driver file is
>> in ht/alo.ktb.  This file imports rockers.kti (actually it imports a file that
>> imports another file).  So, if I leave alo.ktb alone and just change
>> rockers.kti, would the include path be updated only for this file or do I need
>> to copy all the included files?
> Just make a copy of the file you'd like to modify.
>