The content of my key table is as follows :
######################################################## title Pactos #################### # Default Bindings # #################### bind BackSpace KEY_BACKSPACE bind Up LNUP bind Down LNDN bind LeftScroll FWINLT bind RightScroll FWINRT bind Down+RightScroll CHRRT bind Up+LeftScroll CHRLT bind BackSpace+Space KEY_ENTER map Dot1 DOT1 map Dot2 DOT2 map Dot3 DOT3 map Dot4 DOT4 map Dot5 DOT5 map Dot6 DOT6 map Space SPACE On Mon, Jan 11, 2016 at 10:52 AM, Dave Mielke <[email protected]> wrote: > [quoted lines by payman shaykhmehdi on 2016/01/11 at 10:46 +0330] > > >I have defined key table and text table for my device, braille display > >works correctly and all commands works as expected, but the conversion of > >braille dots to ascii (unicode) characters doesn't work.It types '1' (not > >'a') for DOT1 and nothing for DOT2 ,etc. > > > >Is it enough to just enqueue key events or something else needed to type > >correctly? > > Your driver should just enqueue key events. You do need to "map" the dot > keys > (including space), though, in your key table, so that braille reverse > translation for input will be done. > > -- > Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of > God. > Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ > EMail: [email protected] | Canada K2A 1H7 | http://FamilyRadio.org/ > _______________________________________________ > 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
