[BRLTTY] Keypad bindings and copy buffer

[Nicolas Pitre]

On Thu, 9 Aug 2012, Dave Mielke wrote:

> [quoted lines by Nicolas Pitre on 2012/08/09 at 22:50 -0400]
> 
> >OK... Are those events time stamped?  
> 
> The packets are received, and only barely interpreted, by the driver, whereas 
> the events are handled by the core. The device doesn't timestamp the packets. 
> 
> Brltty could add the overhead of arbitrarily timestamping every single key 
> event for all devices (including the keyboard), though. If that's an overhead 
> we're willing to take, it can easily be done. The only negative impact, I 
> suppose, would realistically be on battery drain. It's probably not that much 
> in the overall scheme of things as key presses don't happen all that often.

I was thinking about adding this overhead to the Alva driver only.  If 
no other device is having this issue, this is probably not worth adding 
this complexity to the core.

The driver could withhold any release event for a small delay.  If a 
press event for the same key comes along during that delay then both 
events are discarded.  That's all.  The delay could be configurable 
through a driver parameter if really needed, but this could turn out not 
to be necessary.


Nicolas