[BRLTTY] problem with defining some key bindings

[Dave Mielke]

[quoted lines by payman shaykhmehdi on 2018/05/29 at 10:53 +0430]

>So, why not just enable brltty to accept more than one nonModifier key? 

Because it's not that simple. The format of a command is a basic command plus
options. Changing that would be very invasive and totally not
backward-compatible so there'd need to be a very good reason for doing so.

>In your approach, We need to modify both brltty and Orca, and every time Orca
>adds a command (maybe) we must add a BRL_CMD_... . But if it would be possible
>to handle more than one nonModifier key, We can use Orca commands just by
>defining some key table bindings.

And if Orca ever changed a keybinding then we'd have that very same problem.
It's poor programming style for a communication layer between two aplpications
to depend on the current user interface ideosyncracies of one of them. The
inter-application communication layer should, in other words, be very
well-defined. It shouldn' be volatile in any way so that, if at all possible,
it'll remain stable and backward-compatible.

Also, just as much as I strongly disagree with a useful general capability
being designed for only a single braille device, I equally strongly disagree
with a useful general capability being designed for use with exactly one
graphical screen reader. That's why I believe that brltty should define a set
of useful generic commands for use with graphical screen readers in general,
and then each of them can choose which ones it implements.

-- 
I believe the Bible to be the very Word of God: http://Mielke.cc/bible/
Dave Mielke            | 2213 Fox Crescent | WebHome: http://Mielke.cc/
EMail: Dave at Mielke.cc  | Ottawa, Ontario   | Twitter: @Dave_Mielke
Phone: +1 613 726 0014 | Canada  K2A 1H7   |