> > So you're trying to solve the problem of giving braille device access to > more > Orca commands for a single braille device?
Yes, I'm working on a new braille device. May I suggest a different approach that'd be more useful to everyone? What > about defining more brltty commands, i.e. BRL_CMD_... > So, why not just enable brltty to accept more than one nonModifier key? 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. Another problem that I've encountered is that xbrlapi doesn't send modifiers to applications. For example, Orca ignores any speech output by pressing Control key. I've mapped one key to CONTROL and in my braille driver I enqueue press and release events, but it seems that Orca doesn't receive these events from xbrlapi. Is it possible to catch these events using brlApi? On Mon, May 28, 2018 at 1:19 PM, Dave Mielke <[email protected]> wrote: > [quoted lines by payman shaykhmehdi on 2018/05/28 at 12:32 +0430] > > >Is it possible to bind a combination of braille keys to a combination of > >keyboard keys? > > Yes, and no. What's possible is combining any single key that isn't > defined as > a modifier with any number of keys that are defined as modifiers (shift, > control, alt, etc). > > >I've tried the following bind but it doesn't work : > > > >bind ScreenReader+Dot2+Dot3+Dot4 KEY_INSERT+PASSCHAR+s > > The insert key isn't defined as a modifier. It could be, of course, but it > isn't right now. If it were, then the correct syntax would be: > > bind ScreenReader+Dot2+Dot3+Dot4 PASSCHAR+s+insert > > >I need a lot of these type of bindings for Orca commands, but it seems > that > >it isn't possible? > > So you're trying to solve the problem of giving braille device access to > more > Orca commands for a single braille device? I'm assuming this because no > braille > device that I'm aware of has a key named ScreenReader. > > May I suggest a different approach that'd be more useful to everyone? What > about defining more brltty commands, i.e. BRL_CMD_... - one for each useful > Orca command. Then, say, bind Dots78 + various intuitive combinations of > dots 1 > through 6 to those new commands. Then change Orca to recognize those new > commands and translate them to its own equivalents. If this were done, > then, > almost by magic (your effort, of course), lots of braille users would > immediately gain a lot more functionality when using Orca. > > -- > 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: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke > Phone: +1 613 726 0014 | Canada K2A 1H7 | > _______________________________________________ > 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 >
_______________________________________________ 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
