I think I have used default timeouts, the only timeout value that I have
used in braille display driver is the input of probeBrailleDisplay()
function (==1000).

readBraillePacket() function have been used for reading packets from
device. There is no such delay for DOT keys or keys that are mapped to
Desktop keyboard keys (e.g KEY_BACKSPACE, KEY_CURSOR_UP, ...) but when I
press keys that are bounded to FWINT, braille display reacts slowly.

Is it reasonable to say that because keys such as DOTs and KEY_BACKSPACE
don't execute any command, brltty can handle them faster and so updates
braille display faster?

On Tue, Mar 1, 2016 at 3:41 PM, Dave Mielke <d...@mielke.cc> wrote:

> [quoted lines by payman shaykhmehdi on 2016/03/01 at 13:44 +0330]
>
> >I have experienced delayed responses for FWINLT and FWINRT. Is this kind
> of
> >slowness in executing such commands normal or it is related to braille
> >display driver?
>
> No, it's not normal at all. Perhaps you have an input timeout set too high.
>
> --
> 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: d...@mielke.cc | Canada  K2A 1H7   | http://FamilyRadio.org/
> _______________________________________________
> This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY@mielke.cc
> 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: BRLTTY@mielke.cc
For general information, go to: http://mielke.cc/mailman/listinfo/brltty

Reply via email to