Jason J.G. White (2026/02/28 07:35 -0500): > Sébastien Hinderer <[email protected]> wrote: > > Also, even if there would be the will and manpower to accomplish that > > work, it wouldmean that you'd need to gather the list of allthe function > > keys of all devices, or at least just the function keys of the active > > one. I am not sure how easy it is to do that programmatically. I am not > > saying it is not, I am just sayingI really don't know. > > Yes, I think there would at least need to be an operation to query BRLTTY > for information about the keys and controls of the active display,
It's already possible, see BRLAPI_PARAM_DEFINED_DRIVER_KEYCODES > or, failing that, the manufacturer/model of device being used. Possible, too. See BRLAPI_PARAM_DRIVER_NAME, BRLAPI_PARAM_DRIVER_CODE, BRLAPI_PARAM_DRIVER_VERSION, BRLAPI_PARAM_DEVICE_MODEL, BRLAPI_PARAM_DEVICE_CELL_SIZE, BRLAPI_PARAM_DISPLAY_SIZE and BRLAPI_PARAM_DEVICE_IDENTIFIER. > Every other screen reader I've used has access to the underlying device > controls, with default command bindings for each supported display type. > > As many displays have braille input keys, a common command set can be > assigned to them, eliminating a lot of device-specific configuration. I think what we cannot do at the moment is get both the driver specifi key codes and the BRLTTY commands. So startingfrom BRLTTY commands seems easier and a lower hanging fruit. But this is not to say that the situation could not be improved. Seb. _______________________________________________ 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://brltty.app/mailman/listinfo/brltty
