[BRLTTY] BrlAPI Raw key code mode?

[Mario Lang]

Shérab <Sebastien.Hinderer at ens-lyon.org> writes:

> Mario Lang (2017/07/27 17:17 +0200):
>> Shérab <Sebastien.Hinderer at ens-lyon.org> 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.

This did the trick:

  brlapi_range_t Ranges[1];
  Ranges[0].first = 0;
  Ranges[0].last = 0Xffffffffffffffff;
  brlapi__acceptKeyRanges(BrlAPI->handle(), Ranges, 1);

Now I am getting raw keycodes. very nice!

>> The documentation of "Raw keycode" mode does explicitly state that
>> brlapi_acceptKeyRange() is not necessary.
>
> Yes, I know.

Either the documentation or the code needs to be fixed.
I would vote for making the code do what the documentation claims.

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Blog: <https://blind.guru/>  GitHub: <https://github.com/mlang/>
  .''`. | Twitter: @blindbird23        FaceBook: disyled
 : :' : | SoundCloud: <soundcloud.com/mario-lang>
 `. `'  | YouTube: <youtube.com/user/mlang23>
   `-