[BRLTTY] brltty as a replacement for libbraille

[Ulrich Völkel]

Am 18.03.2010 19:07, schrieb Samuel Thibault:
> Ulrich Völkel, le Thu 18 Mar 2010 12:26:21 +0100, a écrit :
>> As soon as the brltty terminal gets the focus my application
>> receives the key event.
>>
>> The same happens when I compile my app as a console application (with Qt
>> you simply add a "CONFIG += console" parameter to your project file). If
>> I start my app it opens a console and the main window. The main window
>> gets the focus. If I press a key, nothing happens. As soon as the
>> console gets focused the main window receives the key event.
> 
> How do you call enterTtyMode? If you leave tty to -1, libbrlapi will
> automatically get the current console's HWND, yes.
> 

I tried all kind of things. And sure BRLAPI_TTY_DEFAULT was one of those.

>> I searched the mailinglist and found some remarks about passing the HWND
>> of the focused window to brltty but is that true and if so, how do i
>> correctly cast a HWND to an int?
> 
> Just cast it into an int :)
> For 32bit compatibility reasons, Windows will not have >32bit HWNDs.
> 
>> Does anyone have an idea, how to solve the problem?
>> I don't need any focus-handling done by brltty but a quite basic in/out
>> as with libbraille. And all that in a windows gui application.
> 
> Then you can use enterTtyModeWithPath(NULL, 0, NULL); to get root
> control.


I got it. I have to call "brlapi_writeText" first otherwise I get no key
events. After displaying something I get all my events.

Is this behaviour intended?

> 
>> Or is there any application out there that has done something similar so
>> I could look how it is done?
> 
> NVDA does it.

great, python :(

> 
>> btw: brltty, at least in it's default configuration, does not recognize
>> the fourth (from right) of the blue keys on top of the Tieman Voyager
>> display.
> 
> That, however, I can't answer :)

should I file a bug report or mail the maintainer of the voyager driver?

I also have a problem with the voyager displaying gibberish with a
simple brlapi_writeText(0, "abcdefg"). I actually don't think it's a bug
because brltty itself seems to display things correctly.
Anyway, that's for tomorrow.



Thanks for your help!

- Uli