Re: [BRLTTY] BrlAPI Raw key code mode?

[Dave Mielke]

Ranges may make sense in raw mode as one may wish to only capture certain key 
groups. If this is supported then the key press bit should be less important 
than the key itself. In other words, the range mapping priority should be the 
group first, the key second, and the press bit last.

-- 
Dave Mielke   | 2213 Fox Crescent | http://Mielke.cc/
Phone: 1-613-726-0014 | Ottawa, Ontario   | http://Mielke.cc/bible/
EMail: d...@mielke.cc | Canada  K2A 1H7   | The Bible is the very Word of God.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Re: [BRLTTY] BrlAPI Raw key code mode?

[Mario Lang]

Shérab  writes:

> Mario Lang (2017/07/27 16:40 +0200):
>> In fact, I know the core doesn't pass the keypresses on because some of
>> the keys result in BRLTTY playing a sound, as if it were trying to read
>> a screen.  Maybe the detection logic for brl_keyToCommand() is the
>> problem?  Or something else?
>
> See the brlapi_acceptKeyRange function & co. You may need to let BrlAPI
> know which keys your application is interested in. I thought in "raw
> keycode" mode all the keys would be passed to the client by defautl but
> it may not be the case.

The documentation of "Raw keycode" mode does explicitly state that
brlapi_acceptKeyRange() is not necessary.  I will give it a try.
What should I pass?

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Blog:   GitHub: 
  .''`. | Twitter: @blindbird23FaceBook: disyled
 : :' : | SoundCloud: 
 `. `'  | YouTube: 
   `-
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Re: [BRLTTY] BrlAPI Raw key code mode?

[Shérab]

Mario Lang (2017/07/27 16:40 +0200):
> In fact, I know the core doesn't pass the keypresses on because some of
> the keys result in BRLTTY playing a sound, as if it were trying to read
> a screen.  Maybe the detection logic for brl_keyToCommand() is the
> problem?  Or something else?

See the brlapi_acceptKeyRange function & co. You may need to let BrlAPI
know which keys your application is interested in. I thought in "raw
keycode" mode all the keys would be passed to the client by defautl but
it may not be the case.

hth,

Shérab.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Re: [BRLTTY] BrlAPI Raw key code mode?

[Dave Mielke]

[quoted lines by Mario Lang on 2017/07/27 at 09:02 +0200]

>Is there anything that I (with my limited understanding of the core) can
>do to help in this?

The core - see brl_base:enqueueKeyEvent() - already calls api_handleKeyEvent(). 
The rest is up to that function, which should return true if it consumes it and 
false if it doesn't.

-- 
Dave Mielke   | 2213 Fox Crescent | http://Mielke.cc/
Phone: 1-613-726-0014 | Ottawa, Ontario   | http://Mielke.cc/bible/
EMail: d...@mielke.cc | Canada  K2A 1H7   | The Bible is the very Word of God.
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty

Re: [BRLTTY] BrlAPI Raw key code mode?

[Mario Lang]

Dave Mielke  writes:

>>Actually, it seems the HandyTech driver does not support delivering raw
>>key codes yet. It should define the BRL_HAVE_KEY_CODES macro and
>>implement the brl_readKey and brl_keyToCommand methods.
>
> That made sense way back in the days when bindings were hard-coded, but I 
> don't 
> think it's the right way to do it now. My personal opinion is that raw key 
> codes should be the values defined within the key tables. That way, no driver 
> would require any extra support for it.

I totally agree.  As already said in another reply in this thread, being
able to grab keyEvents via BrlAPI would be useful and revive the
current keycode feature, which seems sort of bitrotten to the point of
almost being unusable.

Is there anything that I (with my limited understanding of the core) can
do to help in this?

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Blog:   GitHub: 
  .''`. | Twitter: @blindbird23FaceBook: disyled
 : :' : | SoundCloud: 
 `. `'  | YouTube: 
   `-
___
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty