hi Samuel, Thanks. I used that flag when I used Virtual Keyboard, but missed to use in real device. With the following it looks like it is working fine .\bin\brltty -b fs -xno -p none -A auth=none -l debug -n -e --no-release-device > debug.log 2>&1
Thanks, Siju Samuel On Tue, Jan 14, 2014 at 4:58 PM, Samuel Thibault < [email protected]> wrote: > Hello, > > Siju Samuel, le Tue 14 Jan 2014 16:48:30 -0600, a écrit : > > It looks like after opening connection and entering tty mode, need to > perform > > at least one write first to do subsequent read/write operations. Is this > > expected. > > Possibly. Remember that by default (release mode), on windows, brltty > deinitializes the driver when the focus is on some non-console window, > after having printed that it's not a console window. It thus means that > brltty won't read keypresses any more. A brlapi client being connected > is not enough for making brltty initialize the driver again to get > keypresses. It's only if the client makes some output that brltty will > consider that it has something useful to show, and thus keep the driver > opened and get keypresses. > > Of course, simply switching to non-release mode in the configuration > file will avoid the issue. > > Samuel > _______________________________________________ > 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://mielke.cc/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://mielke.cc/mailman/listinfo/brltty
